| 1 |
Brian Harring posted on Mon, 23 Nov 2009 15:19:00 -0800 as excerpted: |
| 2 |
|
| 3 |
>> "Alternatively, we could simply make portage spawn the mv binary |
| 4 |
>> whenever rename fails (it fails when the source and destination are on |
| 5 |
>> different devices). Although it's relatively slow, it should solve the |
| 6 |
>> problem." |
| 7 |
> |
| 8 |
> Yeah... no. Slowing down the main manager for a thereotical edge case |
| 9 |
> doesn't seem particularly useful to me ;) |
| 10 |
|
| 11 |
I say go for second resolution now, basically using the #1 proposal, and |
| 12 |
apply it to all eapis for the reasons zac outlined, but with a fixed |
| 13 |
effective date say 90 or 180 days out from the council resolution to give |
| 14 |
PMs time to come into compliance. To try for nanosecond resolution now |
| 15 |
is simply letting the complex perfect be the enemy of the simple good, |
| 16 |
when what we have at present is the no-good. |
| 17 |
|
| 18 |
Then make a donsmtimes like the #2 proposal, that individual ebuilds can |
| 19 |
call for specific paths if it's really necessary. It's more work for the |
| 20 |
ebuilder, but that's in relative measure to the slowdown it'll cause on |
| 21 |
two out of three PMs including our core PM, so a bit of discouragement |
| 22 |
from using it could be considered a good thing, tho it would be there, if |
| 23 |
required. |
| 24 |
|
| 25 |
If at some point in the future ns resolution becomes a much bigger issue |
| 26 |
and many ebuilds are using the donsmtimes call, there's nothing stopping |
| 27 |
us from looking at further tightening up the requirements for the general |
| 28 |
case, probably as part of an eapi, then. |
| 29 |
|
| 30 |
-- |
| 31 |
Duncan - List replies preferred. No HTML msgs. |
| 32 |
"Every nonfree program has a lord, a master -- |
| 33 |
and if you use the program, he is your master." Richard Stallman |
Archives