On 5/9/07, Alessio 'mOLOk' Bolognino <[EMAIL PROTECTED]> wrote: > On 00:55 Thu 10 May , Alessio 'mOLOk' Bolognino wrote: > > 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. > > I just realised that you can't print any post-install message if you > can't install it :)
Yeah pre_install would have been awesome, but this fails before that happens. _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
