Denis Dupeyron posted on Tue, 29 Jul 2014 07:58:26 -0600 as excerpted: > [H]ere is what I was instructed to teach recruits back when I became a > recruiter in 2006 or 2007, and what competent developers have been doing > since even before I was a developer: > > The package.mask file is only for temporary masking, even if more or > less long term. Anything that should be permanently masked has no place > in the tree. Live ebuilds should not be keyworded, reflecting the fact > that the code they're pulling has not be tested for any architecture due > to it being live. Moreover, live ebuilds should not be masked as this > results in unnecessary cruft in the package.mask file.
Thanks. That makes sense, tho it does conflict with "content-touchless" bumps from the live ebuild. In the context of that policy and a content-touchless-bump goal, I suppose I'd script the bump, pulling keywords from the highest previous version, prepending the ~ as necessary and inserting them in the keywords line after copying the file from the live-ebuild . That wouldn't be content-touchless, but the touch would be automated so as to avoid mistakes and unnecessary work. -- 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
