On Fri, Feb 20, 2004 at 07:46:58AM +0000, Paul Nasrat wrote: > On Thu, Feb 19, 2004 at 10:06:49AM -0800, Robert Lehr wrote: > > Is this list the correct place to submit a patch for v4.2 or v4.0.4? > > We added a useful feature that we use at Cisco to build our custom RPMs. > > bugzilla.redhat.com -> file as an enhancement against rpm. That way less > likely to get lost. Feel free to mail here for discussion though. > Sure. It is simpler for me to simply cut-n-paste my bugzilla request. I can email the patch to anybody that is interested. At https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116448 I am submitting a patch that implements use of a subdirectory with the %files directive. It is only useful when using a single spec file to build several packages. By specifying a subdirectory of the RPM_BUILD_ROOT, we force RPM to strip that additional component from the pathname of the files loading the files into the RPM. A patch for v4.2 and v4.0.4 is attached to this feature-request. It is used in this manner. %install # do a bunch of installation stuff %{__mkdir_p} $RPM_BUILD_ROOT/{mainpkg,subpkg1,subpkg2} for i in mainpkg subpkg1 subpkg2 do generate_filelist $RPM_BUILD_ROOT/$i > filelist-$i done %files -f filelist-mainpkg -r mainpkg %defattr(-,root,root) %files subpkg1 -f filelist-subpkg1 -r subpkg1 %defattr(-,root,root) %files subpkg2 -f filelist-subpkg2 -r subpkg2 %defattr(-,root,root) We use it for two purposes. First, we build packages that contain files with the same name but different contents. This cannot be accomplished without the feature that we have added. But it is a critical feature for us to the software on our ~400 servers located around the globe. Second, we use it as an easier means of generating file-lists for the sub-packages being created by a single spec file. -- Robert Lehr _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list