sm-discuss AT lists.ibiblio.org
Subject: Public SourceMage Discussion List
List archive
Re: [SM-Discuss] Optional dependencies and dependency mess
- From: Hamish Greig <hgreig AT bigpond.net.au>
- To: sm-discuss AT lists.ibiblio.org
- Subject: Re: [SM-Discuss] Optional dependencies and dependency mess
- Date: Thu, 25 Mar 2004 12:58:23 +1100
-----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)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAYjy/8fSufZR6424RAomjAJ9XVy4foonvTvd/C1dWkSIocQxj0gCeOQuf
XbOLpeacXaVHFyCHCH0r/hc=
=RGtg
-----END PGP SIGNATURE-----
-
[SM-Discuss] Optional dependencies and dependency mess,
Eric Sandall, 03/22/2004
- Re: [SM-Discuss] Optional dependencies and dependency mess, Hamish Greig, 03/22/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Arwed von Merkatz, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Eric Sandall, 03/24/2004
- Re: [SM-Discuss] Optional dependencies and dependency mess, Casey Harkins, 03/24/2004
- Re: [SM-Discuss] Optional dependencies and dependency mess, Andrew, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Hamish Greig, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Casey Harkins, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Hamish Greig, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Casey Harkins, 03/24/2004
- Re: [SM-Discuss] Optional dependencies and dependency mess, Hamish Greig, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Andrew, 03/24/2004
- Re: [SM-Discuss] Optional dependencies and dependency mess, Casey Harkins, 03/25/2004
- Re: [SM-Discuss] Optional dependencies and dependency mess, Hamish Greig, 03/25/2004
- Re: [SM-Discuss] Optional dependencies and dependency mess, Casey Harkins, 03/25/2004
- Re: [SM-Discuss] Optional dependencies and dependency mess, Andrew, 03/25/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Casey Harkins, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Hamish Greig, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Casey Harkins, 03/24/2004
-
Re: [SM-Discuss] Optional dependencies and dependency mess,
Eric Sandall, 03/24/2004
- <Possible follow-up(s)>
- RE: Re: [SM-Discuss] Optional dependencies and dependency mess, evraire, 03/24/2004
Archive powered by MHonArc 2.6.24.