package management



Hi,

Am I the only one who has difficulties from doing package management
in CL? I'm wasting huge resources to deal with that and I'm looking
for a methodology to deal with it once and for all.

Currently on my machines live the following types of packages:

1. asdf-install-ed packages;
2. CVS (and similar) packages;
3. Packages installed using the OS package management;
4. Packages that I developed;
5. Packages that got shipped with other packages;

It's a hell of a job to deal with this without prior planning,
especially if one manages more than one machines.

I have plenty of issues. I update a package to the latest version to
find out that I had to update another package that had higher
priority. Installing new machine is a lot of work. Sometimes the
software works on one of the machines and not on the other. I also
have problems with old FASL files.

How do you deal with the problem? Is ASDF a norm these days? What
about common-lisp-controller - do you use it?


Thanks,

--
Kamen
.



Relevant Pages

  • OT - Ever wonder why?
    ... packages of eight. ... Only in America......do they have drive-up ATM machines with Braille ... On an American Airlines packet of nuts: "Instructions: Open packet, ...
    (rec.sport.billiard)
  • Re: [SLE] A dynamic updates/supplementary server?
    ... the updates and supplementary trees. ... You mean some kind of caching proxy? ... A kind of system that caches all packages, ... especially clear to me how other machines could use this. ...
    (SuSE)
  • Re: Compiling Packages
    ... I have three computers, only one running FreeBSD ... >machines with good network connectivity. ... I've been getting more interested in clustering. ... you build packages over MPI?) ...
    (freebsd-questions)
  • Debian installer public key not available
    ... I have several machines running Debian. ... The following packages cannot be authenticated! ... Install these packages without verification? ... My other machines upgrade fine. ...
    (comp.os.linux.questions)
  • Re: dts on different machines
    ... You will use Agent on/Windows scheduler on many machines to call into DTSRun. ... Remember the storage location of the packages is immaterial, it is where you ask to run from. ... This is often accomplished by starting a SQL Server Agent job on the ...
    (microsoft.public.sqlserver.dts)