| 1 |
On 02/01/17 17:49, Rich Freeman wrote: |
| 2 |
> On Mon, Jan 2, 2017 at 11:56 AM, Kent Fredric <kentnl@g.o> wrote: |
| 3 |
>> On Thu, 29 Dec 2016 17:23:58 +0000 |
| 4 |
>> Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 5 |
>> |
| 6 |
>>> Because it isn't... Are set names atoms? Are package names without an |
| 7 |
>>> associated category atoms? |
| 8 |
>> Sets /are/ still dependency specifications, in that reading, just like |
| 9 |
>> || ( ) groups are dependency specifications, and lists of atoms are dependency specifications. |
| 10 |
>> |
| 11 |
>> Hence, this is an example of in my mind why "atom" is a *better* descriptor than "dependency specification" |
| 12 |
>> |
| 13 |
>> Because it rules out sets and all the other shenanigans. |
| 14 |
> However, in this case why would we want to rule out sets, "and all the |
| 15 |
> other shenanigans?" We've already established that a single stable |
| 16 |
> request bug can apply to multiple package-versions, so why not allow |
| 17 |
> full dependency specifications? If there is a set that describes what |
| 18 |
> needs to be stabilized in an atomic operation, then what is the value |
| 19 |
> in breaking it down into a million separate =-only atoms? |
| 20 |
> |
| 21 |
> If the process becomes further aided by automated tools then using the |
| 22 |
> same dependency specifications as PMS/etc would allow the same code to |
| 23 |
> be used to identify candidate PVs to stabilize. |
| 24 |
> |
| 25 |
> Of course in the most typical case you're stabilizing exactly one PV, |
| 26 |
> but I'm not sure we need to limit the syntax simply because that is |
| 27 |
> all that is required in the most common case. |
| 28 |
> |
| 29 |
I don't think we're writing new tools to do this, we're simply using the |
| 30 |
existing ones better. So, a list of explicit ebuilds by |
| 31 |
Category/Package-Version is what's desired (I believe). But I'll defer |
| 32 |
to kensington/ago who are the ones really using this system in anger ... |
Archives