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

Re: Environment variables in RPM installation scripts

Good question!

Yes, I suppose this would be a simple fix, but... In a few places in the RPM docs, they say that it is not good practice to modify files that were installed from another package. The files I want to modify are not files that "belong" to me.

Specifically, I am modifying the *.repo files in /etc/yum.repos.d. I add my own files, but I want to disable the default fedora files that were installed by yum.

When I uninstall my package, I would simple reverse the patch to restore the default yum config files to their original states.

In any case, I can't add any new files from %files, because it gives me an error saying that these files belong to another package.

I suppose I could install the "updated" files under a new name in a known location, them apply the patch. Would that be the standard way of doing what I'm trying to do?

Thanks again!!

On Aug 7, 2006, at 16:46, David Nečas (Yeti) wrote:

On Mon, Aug 07, 2006 at 04:42:11PM +0900, David Leangen wrote:

The build dir was an example. I guess what I really need is the source.

I want to apply a post-installation patch.

Are you suggesting that I put my patch file with the %files in a
known location and use it from there?

I don't really want to install the patch file as part of the
installation... All I want to do is something like:

patch -p0 < my_patch_file

If you can make the patch at build time why don't you patch
it in %install and package already patched files?


Anonyms eat their boogers.

Rpm-list mailing list
Rpm-list redhat com

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