Eric Edgar:
Catalyst is designed to encourage fixes to bugs. These bugs can get posted
to bugzilla and the ebuilds are fixed for everyone.
Ok, that makes perfect sense! Though the rumours that it's hard being
listened to when posting bugs are turning out true for my second bug (help
me out here, unless I'm being stupid - haven't read the whole ebuild docs -
but this is trivial right?):
http://bugs.gentoo.org/show_bug.cgi?id=172622
So catalyst gets very dependent on portage.
Stephen L. Ulmer:
There is a significant difference in quality between the pure product and
the kludged product -- in maintainability of the system itself and the
meta-system[1].
What I'm saying is: catalyst is awesome and is a few command options away
from being acessible to much more people. You may just want a livecd to use
once and not maintain it (short lifespan games cd's for instance). It's an
option people. Want to use it perfectly ignore the option. Want a quick
dirty built use it that's all :).
Eric Edgar:
Another issue that arises from entering the chroot manually is that the
caches arent necessarily vaild anymore. If you do something really funky
it is possible this will get cached in the caches and could easily mess up
future runs of catalyst.
!Idea! for reproducible results, instead of "logging on" the cd, one could
just point catalyst to a script (that would do only emerge arguments, how
much mess can it make like that?).
Stephen Ulmer:
So putting the philosophy aside for the moment, what are you trying to
accomplish (big picture)?
Now I'm just building a personal livecd to learn catalyst and use my
favourite programs everywhere (eclipse, gcc, gftp, totem, etc). Later the
real objective is top secret :P
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
--
[EMAIL PROTECTED] mailing list
