On 2007-12-17 14:18:07 -0800, Dan Stromberg wrote:

I have a 3 tar archives that I want to package up as rpm's.

Actually, they're already getting packaged up as rpm's, but it's kind of a pain, because the files to include vary from one release to the next. I want to get this more automated.

Wait! Before you fire off a message saying that this part shouldn't be automated, continue reading please :) The tar archives are not full of source code; they're full of binary results and shell scripts. It would be perfectly acceptable to package up every file in each of the tar archives into a distinct rpm, so long as they have the right permissions, owners, %config's, %attr's, etc.

What's the sweet spot of ease vs effectiveness for automatically generating an rpm from such a tar archive?

Can I stuff things like %config and %attr into the %files -f filename, or do these keywords have to go into the %files section of the spec file, beneath the %files token?

I googled about this, but it's hard to get useful hits on things like "%files" and "-f". :) The search terms are too generic.

unpack the tarball in %prep install the files in %install into the %buildroot fill your filelist in %files it is not that much different from packaging from source. you just leave out the build step. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org