Hi everybody,
We are packaging our application using RPMs, and we are having a bit of
a riddle. Our application has the following structure:
<version>
|--- depends
| |--- depA
| |--- depB
| ---- depC
---- folderA
We are packaging version/depends/{depA,depB} together in RPM1.
version/depends/depC is packaged on its own in RPM2, and version in
RPM3.
From RPM dependencies point ov view, we have that
RPM3 requires RPM2 and RPM1
RPM2 requires RPM1
When removing these packages by passing them to RPM -e, the removal
sequence is: RPM3, RPM2, RPM1 (because of the dependencies).
However, as RPM1 and RPM2 are inside the folder <version>, owned by
RPM3, and it gets removed in the first place... the outcome of this is
that there is a folder <version> left hanging around.
I could add on the postun step an "rm -rf <version>" for RPM1, but this
feels wrong. Is there any standard approach to deal with this issue?
Thank you very much,
--
Felix Rubio
"Don't believe what you're told. Double check."
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list
