On Saturday 01 September 2007 17:29:24 wrote Dr. Peter Poeml:
On Tue, Mar 06, 2007 at 04:17:07PM +0100, Marcus
On 2007-03-02 15:14:43 +0100, Robert Schiele
Currently there is no way to link to a package
built on the build
service because if we do so this link will break on every rebuild since
the release number will change.
Because of that I recommmend to automatically create symbolic links
without the version number as we have in the update directories on
. For example:
zypper.rpm -> zypper-0.6.15-0.1.i586.rpm
If we do so we can just link to
. This link
will never break due to an automatic rebuild.
but it i will make the redirector harder.
The redirector works fine with symlinks, as far as I can see.
yes, but symlinks would double the amount of files which needs to be handled.
Given that we do always have a very high load with rsyncd on our servers this
is really a bad idea. Also, the symlinks can be broken during update runs, it
is imho not a good idea to introduce another place which might break
Additionally, it is also a bad idea to point to a rpm directly. An End-User
would have to handle any dependency issues manually (and even search for
missing repositories manually).
What we need is a static URL for installing packages what takes care about
repositories and dependencies. We have that already, if one creates a pattern
file in the build service. But this should work of course also without the
need to create manually patterns for each package. We have the on-the-fly ymp
generation for this, but this does not yet work independend of the version.
A bugreport is open regarding this.
To conclude, I do not think this is a redirector task, this is something which
happen on level on top of it.
And Peter described extensivly further problems with this ;)
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org