Re: Files in build root but not in the file list now a fatal error. Why?

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

 



On Fri, 16 Apr 2004, Christian Goetze wrote:

> I already noticed that RH8 with rpmbuild 4.2.something issued warnings
> about files in the build root but not in the %files list.
> 
> So some developer in my shop got Fedora core 2 which comes with rpmbuild
> 4.3.something, and that warning became a fatal error.
> 
> Is there any way to provide a list or a pattern of files which are OK to
> have in the build root but not in the %files list? In particular, I have
> one file which I don't really want to put elsewhere and which I need to
> leave around to suit rpm: the file containing the file list.
>
Any file is not OK, but what you may be able to do is add said missing 
files to %files list as an %exclude, like:

	%exclude /some/file/in/build/you/don't/want

and then, from what I have seen in the source they get ignored.  I have
not tested this though, so YMMV.  Alternatively, you can delete said 
files in your %install section, so that when it goes to package up the 
files, the unwanted files will not be there.   Look on www.rpm.org, and
I think there is a section on this problem that lists other alternatives.

Cheers...james

> In my rpms, I usually build the install time location using constructs
> such as this:
> 
>   mkdir -p .%{prefix}/bin
>   cp <stuff> .%{prefix}/bin
>   cp -r <morestuff>/lib .%{prefix}
>   ...
> 
> Then I build the file list using find and some patterns to insert %attribs
> if needed, then followed by %files -f filelist. The new system now forces
> me to put this list elsewhere... no real biggy, just a surprise when I
> then latest version...
> 
> Also, people who do the canonical thing, i.e. unpack the source, configure
> with a prefix in the build root, build and install will now have to clean
> out the build tree at the end of the %install section, making it much
> harder to debug things.
This has been going on for a while, and it actually helps more than harms.
Basically, what it prevents is packaging something up that you thought was
the complete set of needed files, but was indeed not the complete set.  
Also, when dealing with open source programs, its mighty handy when going
to a new version of the software, because, it tells you about all the new
files that now appear in your build root that you probably want.

Cheers...james


_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux