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