On 6/3/11 4:09 PM, Chí-Thanh Christopher Nguyễn wrote: > Michał Górny schrieb: >> You could have a 'versioned' ebuild linked to the actual SRC_URI, >> and bump it whenever you notice the upstream tarball changes. This >> would allow users to have the package upgraded automatically. > I don't think this will help users much. It will just make the package > uninstallable between the time the upstream tarball changes and the > package is bumped. > A live ebuild is at least honestly telling users what to expect.
Agreed. The 'version' ebuild linked to the tarball changing in place is actually the current state of non-live ebuilds (by the way, do people responding in this thread actually read ebuilds in question?). This thread is about removing those 'versioned' ebuilds, so your response could be interpret as "don't remove them". But then they're broken, and if I bump them today a few weeks/months from now they'll be broken again. The live ebuild should be more "resilient". >> I think it would be similar to the situation we had with adobe-flash >> packages. > It reminds me more of the (now defunct) live ebuild of chromium-bin Interesting, I was maintaining chromium-bin and I masked it. Doesn't seem similar to me (did you mean google-chrome-bin or similar hacks?).
signature.asc
Description: OpenPGP digital signature
