[pacman-dev] [PATCH] Add information on version comparison to manpages

[Xavier]

On Fri, Jun 20, 2008 at 2:42 PM, Roman Kyrylych
<roman.kyrylych at gmail.com> wrote:
>
> the old vercmp also maintains backwards compatibility,
> i.e. packages that used to have options=('force') (e.g. samba) will
> still have it,
> and packages that used to not have options=('force') when using
> *{rc,beta,pre} won't need it.
> (I didn't counted anything though :-P).
>
> I mostly dislike the change just because it will require
> removing/adding options=('force') to packages
> without a real need (IMO).
> /me shrugs
>

Well I am not sure that is relevant, given the current status of this
force flag.
Half of the packages that used force use the old force=y option which
is no longer supported.
And the big majority of the packagers using options=(force) haven't
been rebuilt and re-added to the database with the new repo-add so
their force flag is currently not in effect.
We have something like 65 official PKGBUILDs with the force options,
and there are less than 10 which actually appear in the databases.
http://www.archlinux.org/pipermail/arch-dev-public/2008-May/006243.html

So my proposal would be to remove force flag from all these pkgbuilds,
and re-add them when they are needed.
If this new behavior of vercmp is kept, this change should probably be
made after 3.2 is released.