Johannes Schauer writes ("Re: Extending the build profile namespace"):
> I agree with Helmut [and implicitly, disagree with Ian]
Well, from what you say things are much further advanced than I
thought. You may well be right - certainly I'm no expert in this area
and I thi
Hi,
Quoting Helmut Grohne (2016-04-25 20:06:07)
> > 2. Require the implementation of a new bootstrap planner which would be
> > able to mine the profile-specific build-dependency information to
> > construct a bootstrap plan.
>
> There is another reason to require a bootstrap planner: pr
Hi,
2016-04-25 19:06 Helmut Grohne:
On Mon, Apr 25, 2016 at 01:28:00PM +0100, Manuel A. Fernandez Montecelo wrote:
Perhaps these OPTIONS and PROFILES should be merged, in a way that if
one is enabled, the other also is. (Is this the plan already?)
They serve different needs. Quite a few opti
On Mon, Apr 25, 2016 at 08:06:07PM +0200, Helmut Grohne wrote:
> because the policy says that nothing must rely on /usr/share/doc/$pkg,
> but when did the last archive rebuild validate that property?
https://piuparts.debian.org/sid-nodoc/ at least tests that installation,
upgrade and removals work
On Mon, Apr 25, 2016 at 01:28:00PM +0100, Manuel A. Fernandez Montecelo wrote:
> Perhaps these OPTIONS and PROFILES should be merged, in a way that if
> one is enabled, the other also is. (Is this the plan already?)
They serve different needs. Quite a few options do not make sense as
profiles. Wh
On Mon, Apr 25, 2016 at 01:44:01PM +0100, Ian Jackson wrote:
> Helmut Grohne writes ("Extending the build profile namespace"):
> > * The nodoc profile is a bit strange. It is supposed to drop
> >documentation from packages or to drop documentation packages. The
> &
Helmut Grohne writes ("Extending the build profile namespace"):
> * The nodoc profile is a bit strange. It is supposed to drop
>documentation from packages or to drop documentation packages. The
>former leads to packages whose content varies with profiles (which
>
2016-04-24 20:08 Helmut Grohne:
* The nocheck profile is the cousin of DEB_BUILD_OPTIONS=nocheck and
must be used in conjunction with that option. Its sole purpose is to
mark droppable dependencies and it seems to be used properly. I would
be happy to see even wider adoption (e.g. #787044)
Hi,
Since Debian Jessie, most of the tooling supports build profiles and a
few packages started using them. I think that it is a good time to
review current build profile usage and extend guidance on adding further
profiles. I will summarize current usage, evaluate current practises and
propose tw
9 matches
Mail list logo
