On Wed, Apr 14, 2010 at 02:43:44PM +0200, Thomas Schmidt wrote:
On 14.04.2010 14:36, Adrian Schröter wrote:
The repserver has already some code to find out if a repo is published already or not.
We could extend that and tell you already, if a package has been published or not.
So we could avoid this additional traffic and IMHO also possible area of bugs.
What do you think about that ?
I don't know. The implemented way is only a head request... Can we rely on the repservers published state? Maybe there get files removed on the public server after being published or sth. like that? We already have a published state in the buildresult, is this related?
The "published" state of the repository doesn't help at all, as you don't know which packages are the unpublished ones if the state is not "published". Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org