Re: Including dependencies



On Sun, 2003-09-07 at 19:04, Jerry Talkington wrote:
> On Sun, Sep 07, 2003 at 03:52:02PM +0200, Jens Bech Madsen wrote:
> > On Sun, 2003-09-07 at 08:13, Jerry Talkington wrote:
> > > On Sun, Sep 07, 2003 at 06:52:56AM +0200, Jens Bech Madsen wrote:
> > > > On Sun, 2003-09-07 at 00:55, Jerry Talkington wrote:
> > > > > Howdy!
> > > > > 
> > > > > Are there any plans on including all of the reqired dependencies (i.e.
> > > > > becoming completely self sufficient,) or has this been decided against?
> > > > 
> > > > How far do you want to take it? XFree86? gcc? glibc? kernel?
> > > 
> > > I'm talking more about things that are included in a GNU system, but not
> > > a *nix.
> > 
> > What things are missing? The autotools are already there as far as I can
> > tell, though no garballs depend on it.
> > 
> > Looking the current list of required things apart from the "sane
> > toolchain":
> > 
> [snip] 
> > which of these would you like included?
> 
> I'll let you know when I finally get this working ;)
> 
> > 
> > Explicitly making the garballs depend on the extra things make it a
> > hassle for the people who already have the stuff installed system wide.
> > Maybe just put them in the bootstrap directory and let people manually
> > add the ones they need/want?
> 
> I'm thinking more of just adding them to the bootstrap dir, and then
> having a meta or bootstrap-meta that would build all of the dependencies
> for a specific OS (i.e. bootstrap/macosx .)
>  
> > Or maybe just maintain your own garballs. I need aspell in a newer
> > version, so I have a garball for that in my own garnome directory. Same
> > with a few other things which aren't available but are needed.
> > 
> > More garballs means more to keep up-to-date for the maintainer.
> 
> I'm volunteering to do that, at least for MacOS X.

Sounds like a very good plan. :-)



Cheers,
Jens




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]