Re: Automake 2.50 migration strategy, as implemented
Ben Pfaff <pfaffben@msu.edu> immo vero scripsit
> For now, it'll be like this. When most packages should have been
> converted to 2.50, I'll downgrade the Depends: to a Recommends:,
> and we'll see what breaks.
I would really recommend doing
autoconf (empty package) Depends autoconf-2.13
autoconf-2.13
autoconf-2.50
And this works the best.
When the transition is over (read: noone depends on autoconf)
You can make autoconf to
Replace, Conflict, and Provides autoconf-2.50.
This is IMO the best way to go, if you do not insist on
everyone moving over to 2.50 immediately.
regards,
junichi
--
dancer@debian.org http://www.netfort.gr.jp/~dancer
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GE d+ s:- a-- C+ UL++++ P- L+++ E W++ N o-- K- w++
O- M- V-- PS+ PE-- Y+ PGP+ t-- 5 X-- R* tv- b+ DI- D++
G e h* r% !y+
------END GEEK CODE BLOCK------
Reply to: