Subject: Re: CVS commit: pkgsrc/x11/xterm
To: Jeroen Ruigrok/asmodai <asmodai@in-nomine.org>
From: Jeremy C. Reed <reed@reedmedia.net>
List: tech-pkg
Date: 08/31/2005 15:54:36
On Sun, 28 Aug 2005, Jeroen Ruigrok/asmodai wrote:

>> Update xterm to 203.
>
> I had already sent my updates to wiz@ and reed@ (since wiz is enjoying
> holidays).  >.<
>
> Since 204 is out already.

I didn't commit since I recieved the utmp_update warning.

But now I realize the difference. The new package (204) installs xterm 
without setuid privilege.

The difference is the install step:

-       $(SHELL) $(srcdir)/sinstall.sh "$(INSTALL_PROGRAM)" xterm$x 
/usr/X11R6/bin/xterm $(BINDIR)/$(binary_xterm)
+       $(SHELL) $(srcdir)/sinstall.sh "$(INSTALL_PROGRAM)" xterm$x 
/usr/pkg/bin/xterm $(BINDIR)/$(binary_xterm)

This sinstall.sh check field 3 to see if previously-installed xterm was 
installed setuid.

So this behaves different based on what is installed.

Since this uses configure script, we can use  --enable-setuid.

What platforms do we want this for?

  Jeremy C. Reed

  	  	 	 technical support & remote administration
 	  	 	 http://www.pugetsoundtechnology.com/