[pacman-dev] Version specs in replaces

Dan McGee dpmcgee at gmail.com
Fri Feb 18 15:08:30 EST 2011

On Thursday, February 17, 2011, Daenyth Blank <daenyth+arch at gmail.com> wrote:
> On Thu, Feb 17, 2011 at 06:00, Allan McRae <allan at archlinux.org> wrote:
>> On 17/02/11 10:42, Dan McGee wrote:
>>> So the first command makes sense, and at least right now we parse
>>> conflicts like we do depends- we allow version specifiers. However, I
>>> found the oddity with REPLACES when doing some archweb work tonight.
>>> Should we be allowing this? Should it be restricted to '=' only like
>>> provides? I'm not sure, so please chime in.
>> I am struggling to think of any case where it would be appropriate to have a
>> version in a replaces entry.
>> Allan
> I ran into this the other day. An example would be python-yaml in
> community. Currently it's for python 2. I'm going to switch it so that
> there's a python2-yaml package and python-yaml would be python3. It
> would make sense for python2-yaml to
> REPLACES=("python-yaml<$py3k_version")

Any other input from anyone before Allan and I lock the definition
down, and then make the code work appropriately?


More information about the pacman-dev mailing list