On 12/08/2009 10:46 PM, Ranguvar wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Tue, Dec 8, 2009 at 14:53, Ionut Biru<[email protected]> wrote:
but it should follow only the beta as
google-chrome-dev should follow only dev
I'm not sure if I'm getting your meaning right, but I think that if a
new beta release arrives,
and it is a version later than the current dev release, -dev should be
updated... same for
- -beta updating to the latest stable if there's not a newer beta.
Users shouldn't have to switch packages to get a newer release if they
use -beta or -dev IMO :)
-- Ranguvar
i don't care how they update. i just don't want to see another n
packages for the same thing just because the maintainer of -dev didn't
updated in the second two after a new version was released.
--
Ionut
