Public SourceMage Discussion List

[Hamish Greig <hgreig AT bigpond.net.au>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 2 Apr 2004 16:29, Seth Alan Woolley wrote:
> On Thu, Apr 01, 2004 at 09:05:01PM -0800, Eric Sandall wrote:
> > Quoting Hamish Greig <hgreig AT bigpond.net.au>:
> > > On Fri, 2 Apr 2004 05:38, Robert Helgesson wrote:
> > > > Elvis should stay. I believe most people cast VIM after the install
> > > > if they like the VI interface but people also have different
> > > > preferences on how to set it up so you'll have to do a cast -r -c vim
> > > > regardless.
> > >
> > > Elvis will stay, but vim should be installable I think (no
> > > optional_depends selected). but the installer doesn't install any
> > > $SPELL_CONFIG files to /etc/sorcery/local/depends/* any more, so the
> > > first sorcery rebuild will ask the user how they want it configured.
> >
> > Ahh, I like that setup. ;)
>
> As long as our ISOs contain spells built with the default configuration,
> I will be happy with no SPELL_CONFIG files.  However, I would like to
> have a sorcery rebuild after install have the same default configuration
> but just be optimized.  It just seems to be more consistent that way and
> will make irc troubleshooting easier.  Is this possible?

I don't see how at the moment, sorcery checks for $SPELL_CONFIG regardless of 
entries in /var/state/sorcery/depends, and reruns the depends queries if no 
$SPELL_CONFIG is found. That is all cast -r does, is remove $SPELL_CONFIG.
But cast --queue deosn't seem to honour -r and sorcery rebuild doesn't take 
that option at all, so the compromise was to remove $SPELL_CONFIG, otherwise 
users were stuck with the options the spell was built with, unless they new 
to delete the $SPELL_CONFIG files or run cast -r for every spell in the 
packages file.
IMO it was a bug in ISO's previous to 0.8.1 (i think that is the first one I 
did, and when I removed all $SPELL_CONFIG) that the user didn't get asked for 
their preferences when rebuilding for their architecture and optimizations. 
http://bugs.sourcemage.org/show_bug.cgi?id=4628


>
> Note for the future:
>
> And you mentioned the perl dependency for linux ... I'd like to have the
> option to not have perl in the basesystem.  In fact maybe we need to
> make a distinction between "runtime_depends" and "build_depends" if it's
> not both.  That way it could cast (as in resurrect if already built)
> perl, build linux, and then dispel perl when the last spell that needed
> it in the install list completed (while optionally keeping a cache
> laying around).  If we wanted to have more fun, gcc itself could be
> eliminated in that way and only resurrected for stuff that needed it.
> This would make it really easy to copy a bunch of caches over and since
> most stuff doesn't need a runtime_depends on the full gcc, we could make
> zaurus/embedded/server ports really easy.  runtime_depends don't have to
> be dependency ordered during building, as well.  Anybody following me?

yes runtime_depends and build_depends are definitely needed, only runtime 
depends should be installed by the ISO, and  I have specifically not checked 
for depends on the "must have" list because it's self contained and it's 
uninstalled depends(according to sorcery) are only build_depends. The 
Optional list does need depends checked because of runtime dependencies, and 
at the moment installs some build_depends like libtool and autoconf because 
it doesn't have a way to exclude them, it sees a depends as a depends.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAbQ/X8fSufZR6424RAuYhAJ9kTs6fFY7aoz9afnlIgtbX2VMRmgCfWHe2
jd+DZzZXN35J+6je3Twue+4=
=tnJx
-----END PGP SIGNATURE-----