> > In /my/ situation I build a number of test packages that > are subsets of > > what is built from a source tarball, and I actually want > %files to be my > > way to pick-and-choose which bits I want to go into my > package, I think > > it's a horrid kludge to make, install, and then at the tail end of > > install, go remove a bunch of stuff that just got > installed. I'll have to > > go experiment with %exclude, I've heard it mentioned but not seen it > > documented. > > Why not make your various test pacakges different subpackages? I suppose there's a scenario here that might work. There might be something I could do with a subpackage I don't bother to use that left rpm thinking there weren't any unpackaged files. I haven't looked into the practicality of that. My point was just that in some of my uses of a package creation tool, I want to be able to say "in of that tree over there, put these files in a package" and the new rpm default is for me not to be able to do that, because it will inform me that I didn't package everything in the place I pointed to. Which, in these cases, I knew :-) and it was what I intended. And is quite different than any package creation tool I've ever used... previously, they've all defaulted to believing I knew what I was doing when I gave them a specific list of things to put in the package. _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
