On Thu, Apr 21, 2005 at 12:13:38PM +0200, Matthias Kurz wrote: > All packages with the same %name are the same package. All packages > except the one with the newest build date are old packages. > Removing everything from RPM/PKG is not very practical, because one > needs all (binary) packages e.g. when a new machine is installed or > when machines with older software than the build machine are upgraded. > And rebuilding everything all the time is not very elegant and quite > time-consuming.
Any update (-U) will rebuild all packages involved and ignore whatever is in RPM/PKG. If the repository contains source packages this means: recompilation. If the repository contains binary packages this means: download. If a machine is newly installed there is nothing in RPM/PKG. If a machine is upgraded then it doesn't matter what is in RPM/PKG. Different versions are ignored anyway. Packages in RPM/PKG are only relevant when you do not upgrade but reinstall the version (with the same options or a superset of the options) that was once installed. > But. To solve the problem of duplicate packages in the "build" part > probably adds too much complexity in the wrong place. I think it would > be better (easier ?) to put this functionality in the "index" part. E.g. > an option -d for "delete older versions of a package". I do not really understand your setup. Do you compute the index directly from RPM/PKG on the build host ? Greetings, -- Michael van Elst Internet: [EMAIL PROTECTED] "A potential Snark may lurk in every tree." ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List openpkg-users@openpkg.org