On Mon, Apr 17, 2006 at 11:47:56AM -0400, Steven M. Bellovin wrote:
>On Mon, 17 Apr 2006 11:18:14 -0400, Johnny Lam <jlam@pkgsrc.org> wrote:
>
>> Is anyone else using the pkgsrc stable branch?  If so, how do you use it?

I generally put this in root cron with a new install,

PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/pkg/sbin:/usr/pkg/bin:/usr/local/sbin:/usr/local/bin:/root/bin:/var/qmail/bin
15 2	* * *	cd /usr/src && cvs -q upd -dP && echo && cd /usr/pkgsrc && cvs -q upd -dP
00 4	* * *	grep -vE '^Pullup ticket' /usr/pkgsrc/doc/CHANGES-pkgsrc-* |sed -n '1!G;h;$p'
00 4	* * *	printf "pkgsrc updates available\n\n" ; pkg_chk -fun | grep -v /usr/bin/env | sed -e 's/.* //' | while read p; do cd /usr/pkgsrc/`pkg_info -Q PKGPATH $p` && echo $PWD; done
# cd /usr/pkgsrc && cvs -q upd -dP -r pkgsrc-2006Q1 .
# when the pkgsrc tools are out of date...
#cd /usr/pkgsrc/pkgtools/pkg_install && /usr/bin/make clean && /usr/bin/make update

It's a little broken atm, but mostly works, would be nice if
pkg_chk could be made to download needed sources ("pkg_chk -fun"
doesn't work as expected) and report which pkgsrc directories need
make update...


>I'll tell you something you don't want to hear -- I tried it, but I gave
>up.  The problem is that security patches weren't pulled up quickly enough
>to the branches.  On stable machines, those are my primary reason for
>recompiling.

humm, I didn't realize there was a security lag between stable
and HEAD. in any event, with various pkgtools I didn't notice
any serious serious exposure (maybe I should look closer at TODO
issues...).  I'd like it if security in stable was a high
priority. :)

moving from 2005Q4 to 2006Q1 was pretty much a breeze (few minor
pkgtools command line issues), I really like the "every quarter
model" and I look forward to trying pkg manager.

Thanks for all the hard work on pkgsrc!

// George


-- 
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org