On Fri, Apr 22, 2005, Matthias Kurz wrote:
I have one build host for every platform/release. There the packages
are compiled from sources, leading to binary packages under RPM/PKG. In
this RPM/PKG i run openpkg index and it is mounted inside a hierarchy
that is accessible over anonymous ftp.
On Thu, Apr 21, 2005, Michael van Elst wrote:
On Thu, Apr 21, 2005 at 12:13:38PM +0200, Matthias Kurz wrote:
[...]
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.
Maybe it
On Fri, Apr 22, 2005 at 08:45:23AM +0200, Matthias Kurz wrote:
On Thu, Apr 21, 2005, Michael van Elst wrote:
On Thu, Apr 21, 2005 at 12:13:38PM +0200, Matthias Kurz wrote:
[...]
Packages in RPM/PKG are only relevant when you do not upgrade
but reinstall the version (with the same options
On Wed, Apr 20, 2005, Michael van Elst wrote:
On Wed, Apr 20, 2005 at 01:40:22PM +0200, Matthias Kurz wrote:
[...]
It would be nice to have an option that removes all old versions of a
package from $prefix/RPM/PKG, when a new build succeeded.
Maybe, but what is 'an old version of a
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.
On Tue, Apr 19, 2005, Etienne-Hugues Fortin wrote:
Hi,
I've installed openpkg on a few servers up to now and for the first time,
I decided to investigate why I'm unable to fetch RPM directly from the ftp
url. After installing the base openpkg package as well as openpkg-tools,
I've tried
On Wed, Apr 20, 2005 at 01:40:22PM +0200, Matthias Kurz wrote:
I also recommend to use -Uua or to remove everything from $prefix/RPM/PKG
before running openpkg build.
-U always includes -u, the build script cannot easily check wether
a binary package in RPM/PKG was created from current sources
