Re: Removing an RPM package from within another RPM package...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry about that.  I didn't read the original mail closely enough.

On 5/10/06, Luciano Miguel Ferreira Rocha < strange@xxxxxxxxxxxxx> wrote:
On Wed, May 10, 2006 at 05:15:21PM -0400, Russell Harrison wrote:
> On 5/10/06, Luciano Miguel Ferreira Rocha
>
> >On your new A, add an "Obsoletes" tag:
> >Obsoletes: B
>
>
> This will burn you later.  Say you decide you do want B at a later date.  If
> you don't remember to use A you can't install B.  Also if you try and
> install something that requires B package management platforms will pull in
> A instead.  Which won't have the libraries the new package needs.
>
> Obsoletes should only be used when package A replaces the functionality of B
> and is intended to be a complete replacement for it.

Which is the case:
"I have recently moved all components & functionality from B.rpm into A.rpm."

--
lfr
0/0


_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list



_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux