Besides a call to /sbin/chkconfig perhaps I see no reason for anything
to be done in %post, %preun etc. in a setup like the on you describe.
These "scripts" are supposed to be used for very simple and very unlikely
commands like adding a user or a service to boot, they should not install
or remove files (directly) of any kind, there are other sections that
have the appropriate mechanisms to do that and detect problems at rpmbuild
time instead of when you are installing/uninstalling.
----- Original Message -----
From: "Mark Bidewell" <mbidewel(a)gmail.com>
To: "Development discussions related to Fedora"
Sent: Saturday, December 1, 2012 8:46:52 PM
Subject: Re: Yum Package Remove Order
On Fri, Nov 30, 2012 at 10:54 PM, Adam Williamson <
awilliam(a)redhat.com > wrote:
On Fri, 2012-11-30 at 17:24 +0100, Nicolas Mailhot wrote:
> Le Ven 30 novembre 2012 15:11, Mark Bidewell a écrit :
> > I have been working on packaging software into RPMs for my
> > company. These
> > RPMs create directories in %post into which dependent RPMs
> > install
> > components.
> You need to create those directories in %install and have your
> package own
> them in %files, and have dependant rpms depend on your package then
> everything will work fine
Or for bonus points, the app itself ought to create the directories
the first place, if they're associated with the app. Packages should
only create directories for stuff that's added as part of the
not part of the software per se - say, you're including a convenience
script which is not upstream, or moving the icons around, or
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca : adamwfedora
devel mailing list
Here is the setup we have.
1) An RPM which creates a raw JBoss install
2) An RPM which sets up a specialized server config (based on the
default config from 1) with common configuration
3) RPMs containing WARs (and configuration).
The reason we encounter the CentOS 5 bug is that the when the RPM in
2 uninstalls, it removes the server config and with it the WARs from
3. Is there a better way?
devel mailing list