On 13:48 Wed 09 May , Aaron Griffin wrote: > On 5/9/07, Jaroslaw Swierczynski <[EMAIL PROTECTED]> wrote: > > How about releasing one last pacman2 with those dependencies added, > > then wait, say, two weeks before moving pacman3 to current? > > The problem here is that the pacman2 upgrade would have the exact same > issue. It would require bug fixes to the 2.X codebase. And even > then, users may miss the 2.X upgrade (someone who -Syu's once a month, > for instance) and hit the same issue.
I think a VERY BIG post-install message would be useful too. -- Alessio 'mOLOk' Bolognino Arch Linux Trusted User Public Key @ http://themolok.netsons.org/uploads/themolok.asc Key ID = 1024D / FE0270FB 2007-04-11 Key Fingerprint = 9AF8 9011 F271 450D 59CF 2D7D 96C9 8F2A FE02 70FB
pgpPuDzkDJ72T.pgp
Description: PGP signature
_______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
