Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Optional dependencies and dependency mess

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Casey Harkins <charkins AT upl.cs.wisc.edu>
  • To: Hamish Greig <hgreig AT bigpond.net.au>
  • Cc: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] Optional dependencies and dependency mess
  • Date: Wed, 24 Mar 2004 20:03:37 -0600 (CST)


On Thu, 25 Mar 2004, Hamish Greig wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, 25 Mar 2004 12:48, Casey Harkins wrote:
> > On Thu, 25 Mar 2004, Hamish Greig wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > A second method, which I haven't thought through at all, would be
> > > for /var/state/sorcery/depends to only be changed after a successful
> > > cast, and for individual spells depends to be listed
> > > in /etc/sorcery/local/depends/$spell (and SPELL_CONFIG moved
> > > to /etc/sorcery/local/configs/*).
> > > I am not sure that this second method would be as beneficial to
> > > resurrect and binary installs (from ISO or network installs) so maybe a
> > > combination of the two would be most useful.
> >
> > I think the second method would work just as well. The depends info could
> > easily be extracted (since it is just a file in the cached archive). It
> > could then be excluded when extracting the cache (i.e. resurrect), or
> > sorcery could just let it install the file instead of creating it itself.
> > I think using /var/state/sorcery/depends/$spell would be better than /etc,
> > since it is state information for the spell. The current flat depends file
> > could then be rebuilt from /var/state/sorcery/depends/* sort of like the
> > codex.index files are built. This has the slight advantage over the first
> > method by not dirtying the .tar.bz2 with trailing garbage (though
> > tar/bzip2 don't seem to mind).
> >
> > -casey
>
> for efficient ISO/network installs the depends need to exist within the
> cache
> tarball I think. recording data in a seperate file would work for a running
> system, but for installing, the cache tarball should be a standalone
> package
> relying on no external files. (like nearly all the other package managers
> do)

Right, but the depends file would be in the cache. It would be created
upon casting in /var/state/sorcery/depends/$spell. This file would be
tracked by sorcery (just like the install, md5, compile logs) and
therefore be in the cache tarball.

To resurrect, this file could be extracted individually and examined to
determine dependencies. I think this would be just as effective as the
first method.

-casey




Archive powered by MHonArc 2.6.24.

Top of Page