Ainsi parlait Luca Berra :
> On Tue, Aug 05, 2003 at 10:26:25PM -0700, Ben Reser wrote:
> >Some of us are already maintaing the packages for multiple distro
> >releases. For a variety of different reasons... Using on a different
> >distro version locally, club, personal tress, etc... There's probably
> >not enough time to spend to do it globally, but I'm going to be really
> >opposed to saying that I can't maintain that backwards compatability in
> >packages I want it in because it's exceedingly tedious to maintain two
> >sets of packages when I can maintain one that builds both places.
>
> 100% with you
It doesn't infirms my initial point:
- backward compatibility has a cost
- having just some packages supporting it by packager choice makes no sense
I'd be personaly in favor of ensuring backward compatibility with current
stable release, as it would reduce a bit the current release/forget mdk
strategy effect, but as a global policy issue, and provided it could be done
otherwise as introducing conditional macros everywhere in all spec files.
Just releasing an updated rpm package for stable release with missing macros
for instance.
--
Guillaume Rousse
When a student asks for a second time if you have read his book report, he did
not read the book.
-- Rominger's Rules for Teachers n�1
