On Thu, 2010-08-12 at 10:23 -0500, Bob Archer wrote: > > How to avoid the .svn directories while preparing rpm packages? > > When I am trying to do rpmbuild ,it is also taking all the .svn > > directores recursively ,Which I don't want to see in the rpm > > packages > > since we send to clients. I tried with %exclude but did not work. > > Do > > any one has this problem? > > You should probably export your working copy to a new folder and build your > package from that. An export does not include the .svn folders. > > BOb >
How are you preparing rpm packages? I have a tool svndownstream that we use to package up workareas or export revisions from a URL into a tarball and loose files that can be used in OBS (which uses rpmbuild at the lower levels). It may be useful for you. http://www.gitorious.org/cray-obs/svndownstream It is smart enough to understand which files haven't been added to Subversion yet or have been deleted, so it's useful for developers doing test builds before checkins and it will ignore all the ? status derived files. svndownstream config -i obs <name>.spec svndownstream update ~/obs If you want just the Subversion to Tarball bit that's in http://www.gitorious.org/cray-obs/svndownstream/blobs/master/svndownstream/subversion.py There's also support for injecting svn info, like the URL or revision into files that rpmbuild can use.
