This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [HEADSUP] Base category
- From: Andrew Schulman <schulman dot andrew at epa dot gov>
- To: cygwin-apps at cygwin dot com
- Date: Sat, 06 Dec 2014 13:52:45 -0500
- Subject: Re: [HEADSUP] Base category
- Authentication-results: sourceware.org; auth=none
- References: <20141206165700 dot GW3810 at calimero dot vinschen dot de>
> isn't it rather annoying that even Base packages have dependencies
> outside the Base category? So, even if I perform a plain Base-only
> installation, I get asked if dependencies shall be fullfilled, which, as
> a question, is more than borderline anyway.
>
> Therefore, shouldn't we put all packages Base packages depend on into
> Base as well?
I can't find it in the archives now, but a year or two ago we talked about
this in the context of libargp. There's a Base package (can't remember
which one) that depends on libargp. But the consensus at the time was that
we shouldn't put libargp into Base, because if the other package stopped
requiring it, it wouldn't belong there on its own.
So if we're talking about permanently adding those other packages to the
Base category, I don't agree. But it we're talking about adding them to
Base automatically only as long as another Base package requires them, then
I guess that's fine.
Andrew