Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Andreas Metzler
Hello, I know this is a standard szenario, but the natural solution conflicts with suggestions in policy. When jumping from 4.3 to 4.5 I'd like to rename pgrep to pcregrep and to provide seamless upgrades I'd introduce a dummy package pgrep depending on pcregrep, however replaces/conflicts gives

Re: Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Colin Watson
On Sun, Mar 07, 2004 at 11:23:40AM +0100, Andreas Metzler wrote: When jumping from 4.3 to 4.5 I'd like to rename pgrep to pcregrep and to provide seamless upgrades I'd introduce a dummy package pgrep depending on pcregrep, however replaces/conflicts gives me a headache. Package: pcregrep

Re: Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Andreas Metzler
On 2004-03-07 Colin Watson [EMAIL PROTECTED] wrote: On Sun, Mar 07, 2004 at 11:23:40AM +0100, Andreas Metzler wrote: When jumping from 4.3 to 4.5 I'd like to rename pgrep to pcregrep and to provide seamless upgrades I'd introduce a dummy package pgrep depending on pcregrep, however

Re: Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Colin Watson
On Sun, Mar 07, 2004 at 01:17:46PM +0100, Andreas Metzler wrote: On 2004-03-07 Colin Watson [EMAIL PROTECTED] wrote: On Sun, Mar 07, 2004 at 11:23:40AM +0100, Andreas Metzler wrote: When jumping from 4.3 to 4.5 I'd like to rename pgrep to pcregrep and to provide seamless upgrades I'd

Re: Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Andreas Metzler
On 2004-03-07 Colin Watson [EMAIL PROTECTED] wrote: On Sun, Mar 07, 2004 at 01:17:46PM +0100, Andreas Metzler wrote: On 2004-03-07 Colin Watson [EMAIL PROTECTED] wrote: On Sun, Mar 07, 2004 at 11:23:40AM +0100, Andreas Metzler wrote: When jumping from 4.3 to 4.5 I'd like to rename pgrep

Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Andreas Metzler
Hello, I know this is a standard szenario, but the natural solution conflicts with suggestions in policy. When jumping from 4.3 to 4.5 I'd like to rename pgrep to pcregrep and to provide seamless upgrades I'd introduce a dummy package pgrep depending on pcregrep, however replaces/conflicts gives

Re: Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Colin Watson
On Sun, Mar 07, 2004 at 11:23:40AM +0100, Andreas Metzler wrote: When jumping from 4.3 to 4.5 I'd like to rename pgrep to pcregrep and to provide seamless upgrades I'd introduce a dummy package pgrep depending on pcregrep, however replaces/conflicts gives me a headache. Package: pcregrep

Re: Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Colin Watson
On Sun, Mar 07, 2004 at 01:17:46PM +0100, Andreas Metzler wrote: On 2004-03-07 Colin Watson [EMAIL PROTECTED] wrote: On Sun, Mar 07, 2004 at 11:23:40AM +0100, Andreas Metzler wrote: When jumping from 4.3 to 4.5 I'd like to rename pgrep to pcregrep and to provide seamless upgrades I'd

Re: Renaming a package, proper values for replaces/conflicts?

2004-03-07 Thread Andreas Metzler
On 2004-03-07 Colin Watson [EMAIL PROTECTED] wrote: On Sun, Mar 07, 2004 at 01:17:46PM +0100, Andreas Metzler wrote: On 2004-03-07 Colin Watson [EMAIL PROTECTED] wrote: On Sun, Mar 07, 2004 at 11:23:40AM +0100, Andreas Metzler wrote: When jumping from 4.3 to 4.5 I'd like to rename pgrep