Re: updating packages

I'm sort of fed up with packaging systems. They all seem to make short sighted assumptions about where files go. Not every machine is a single user system. Sometimes you want something different: a private copy or shared within a group of users or global to a machine or shared in a network file system. And for each package system you have to learn how to do which of those setup tasks you want for that kind of system. Every non trivial system has its own package system because it can do it "better." So we have packaging systems for Emacs, Perl, Python, Ruby... and vendor systems like RPM and Deb and Rocks and the Windows installer and the somewhat independent tools like Puppet, Chef, CfgEngine GNU Stow. Or build it yourself with autoconf or cmake from sources in some tarball at an ftp site or git or hg or svn or cvs or bzr. It's nice be familiar various tools but it's also necessary to get some work done... Sorry for the rant. I like that xemacs is somewhat smart and dynamically builds up a good load-path. And if its packaging system can guide me through steps to do the particular kind of setup I need then I'll have to look at it again. When I have some time. -- Jeff Baird <Jeff_Baird(a)cs.cmu.edu&gt; _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta