Jeremy Katz <katzj@xxxxxxxxxx> writes:
> On Tue, 2004-05-18 at 23:15 -0400, Daniel J Walsh wrote:
>> Policy rename dilemma. I have a version of policy ready to go that
>> supports both strict and targeted policy. The version I wrote creates
>> targeted policy as policy and policy-sources and the strict as
>> policy-strict and policy-strict-sources. The problem with this is that
>> if I put it in Rawhide people upgrading will switch from strict policy
>> to relaxed and require a relabel. If I change it to strict equals
>> policy and policy-sources, with policy-targeted and
>> policy-targeted-sources, than I am stuck with that even though
>> policy-targeted will be the default in FC3, which seems wrong.
>
> You could do policy-strict Obsoletes: policy < newver. Then if you do
I tried versioned obsoletes with some Perl packaging for a while and,
IIRC, rpm ignored the version completely. Or maybe it was up2date
that did. Something handled it wrong, don't recall the details but
the net result was 'doctor, it hurts when I do this. 'don't do that.'
It may be fixed now, but this wasn't too far back.
Chip
--
Chip Turner cturner@xxxxxxxxxx
Red Hat, Inc.
