* Re: [gentoo-dev] Dependencies default to accept any slot value acceptable (:*), can we default to :0 instead?
@ 2013-12-09 3:19 99% ` heroxbd
0 siblings, 0 replies; 1+ results
From: heroxbd @ 2013-12-09 3:19 UTC (permalink / raw
To: gentoo-dev
[reordered to ease replying]
Rich Freeman <rich0@gentoo.org> writes:
> Now, perhaps a more balanced approach might be to mask it and give 15
> days notice on -dev, and then it can be unmasked. Anybody who cares
> about the library can test the new version, and if necessary update
> their dependencies to use the previous slot only (and if 15 days isn't
> enough time they can just update the dep right away and then update it
> again after they get around to testing it). Those who don't want to
> have to deal with that can just define their slot dependencies
> explicitly so that this policy will never apply to them.
Good idea!
> The problem with this is that it puts the onus on the person who wants
> to make forward progress (adding support for a new library version).
> That means that they have incentive to either not bother with the new
> library version (causing Gentoo to stagnate), or use hacks like giving
> the library a new name (which we have examples in the tree of).
> In order for a QA policy to be effective it has to either be minimally
> intrusive, or make the cost of compliance lower than the cost of
> workarounds or benign neglect. People don't HAVE to maintain
> packages, after all...
I agree with that. We are all aware that every gcc slot bump costs so
much work (and frustration).
At the same time, it worth the hard work for a well-organized tree and
flexibility.
The only draw back is lack of man power to do it right like bug
493652. Yes, when a library introduces a new not fully compatible
version, it naturally implies a lots of work to do for downstream like
us. There is no escape: If we hack a versioned library name, it will
bite us in the future. The question becomes: Who should do this heavy
lifting?
This is a glitch in the amount of work needed when a single-slotted
library suddenly becomes slotted. IMHO, let's form a slotting group in
the reformed QA team who will donate manpower for such situation to aid
the library maintainer. Anyone who wants to make forward progress but
does not have enough time seeks help to the slotting group.
What do you say?
Benda
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2013-12-08 16:56 [gentoo-dev] Dependencies default to accept any slot value acceptable (:*), can we default to :0 instead? Tom Wijsman
2013-12-08 17:19 ` Andreas K. Huettel
2013-12-08 19:14 ` Ulrich Mueller
2013-12-08 19:39 ` Rich Freeman
2013-12-08 20:01 ` Ulrich Mueller
2013-12-08 20:17 ` Rich Freeman
2013-12-09 2:37 ` heroxbd
2013-12-09 2:55 ` Rich Freeman
2013-12-09 3:19 99% ` heroxbd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox