Yes, Panu's right. The spec file I pasted is a simple example which only installs one script. But every time I build a new version, I will make some changes in the file software.sh. So if I remove the version# in the installation path, the "rpm -i" command will fails because of conflict file if a previous version already installed. Thanks, Wendy -----Original Message----- From: rpm-list-bounces@xxxxxxxxxxxxx [mailto:rpm-list-bounces@xxxxxxxxxxxxx] On Behalf Of Panu Matilainen Sent: 2013年11月27日 15:40 To: rpm-list@xxxxxxxxxxxxx Subject: Re: Get the command in the rpm spec On 11/27/2013 06:09 AM, Greg Swift wrote: > On Tue, Nov 26, 2013 at 9:55 PM, Greg Swift <gregswift@xxxxxxxxx> wrote: > >> >> d) if your weren't using a versioned directory the -i would break >> because the filename would be the same, and thus the packages would conflict. >> > > So I'd like to retract this. in your case it doesn't happen. Its > seems to only care about binaries and libraries? not sure what the logic on that is. When a file is identical between two (or more) packages it doesn't cause a conflict, its simply shared among those packages and only removed when the last package owning it is removed. - Panu - _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list
