On Mon, 9 Sep 1996, Buddha Buck wrote:
> That sounds good... However, please -DON'T- mark popclient as Replaces:
> netstd. As far as I understand, Replaces should only be used when one
> package completely replaces another's functionality, and I don't thing
> popclient replaces all of netstd.
> That sounds good... However, please -DON'T- mark popclient as Replaces:
> netstd. As far as I understand, Replaces should only be used when one
> package completely replaces another's functionality, and I don't thing
> popclient replaces all of netstd.
I thought it meant the package replace
> Michael Shields wrote:
> >
> > > Suggestions:
> > >
> > > 1) Remove popclient from netstd, or
> > > 2) Update the popclient in netstd and eliminate the separate package.
> >
> > I had already packaged and uploaded popclient before noticing this.
> > I'm not sure it needs to be in netstd; if we
Michael Shields wrote:
>
> > Suggestions:
> >
> > 1) Remove popclient from netstd, or
> > 2) Update the popclient in netstd and eliminate the separate package.
>
> I had already packaged and uploaded popclient before noticing this.
> I'm not sure it needs to be in netstd; if we take it out, I ca
Package: popclient, netstd
Version: 3.05-1, 2.07-1
The netstd package provides popclient 2.21, and the popclient package
provides popclient 3.05. These two versions aren't completely
compatable.
Neither package conflicts with the other, yet both provide
/usr/bin/popclient, /usr/man/man.1/popc
> Suggestions:
>
> 1) Remove popclient from netstd, or
> 2) Update the popclient in netstd and eliminate the separate package.
I had already packaged and uploaded popclient before noticing this.
I'm not sure it needs to be in netstd; if we take it out, I can
trivially upload another version that
6 matches
Mail list logo
