On Sun, 2005-10-30 at 18:38 -0500, Jim Popovitch wrote: > Is there a way for us to develop packages that don't require updating > ALL the files in a package? For instance, in the latest glibc-common > update only a few lines of source code changed. Yet on my test system I > see a hundred files (mostly locale files) that are reported as being > changed by tripwire, but probably didn't really require a change from > the ones in the earlier package. Is this a nuisance that we could > prevent if we only released packages that were built on a common build > system? > > Just looking for more insight into keeping things consistent. ;-) The problem is that a package rebuild will rebuild all files within the package. There isn't a way around that. -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating -- fedora-legacy-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-legacy-list
