Mailinglist Archive: opensuse-buildservice (314 mails)

< Previous Next >
Re: [opensuse-buildservice] One common community repository in BuildService?
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Thu, 24 Jan 2008 09:40:03 +0100
  • Message-id: <200801240940.03205.adrian@xxxxxxx>
On Thursday 24 January 2008 09:17:31 wrote Michal Vyskocil:
Hi all,

some of other distributions has some kind of a community repository. The
Ubuntu guys has universe/multiverse repos, there are Arch User repository
for Arch Linux, the Gentoo has Sunrise Overlay, etc.

The OpenSUSE has a BuildService, which is an excellent building system for
maintenance of the community repository. But the OpenSUSE also has a
several hunderds of specialized repos and that is too much complicated for
many users. Why are there 10 games: repositories? Or a small one like
devel:languages:smalltalk with 2 packages only? I think, that using of
several different repos should consists the package conflicts on client's
side. And some peoples hates this system, because is too much complex.

Are there any technical problems to create a one (or a few) common
community repository in BuildService? Do you think, that the existing state
is good, or it'll be fine to have a one big community repositry?

I agree that some of the projects should get packed together and one should
look at this.

But having only project would have several dis advatanges:

* All needs to use same project setup config, means building for the same
base distributions and using same package project config.

* write access to that project needs to be either more strict and less open
than atm, or if you keep it open, no one can really trust this repo and you
should not add it. Keep in mind that such a repo would be a perfect target
for someone who wants to steal your credit cards numbers for example, what
would be really easy than (no, I will not describe how;).

* several projects do conflict even at build time. We had the problem in the
past that submissions to the old "supplementary" to fix A destroed B.
(It was really hard for me sometimes to keep KDE working in that and often
enough even more low level stuff like apache got crashed but other peoples
submissions. And at that time only less than 10 people have commited to
that. Imagine what happens with write access to more than 100 people)

* More people with write access will keep the project building, that means in
worst case it will get never get released to the ftp server.

I think we do our best to improve the handling of multiple repos, something
what we need anyway. Esp. the YaST meta package installer from Benjiman has
helped here a lot already.

However, when you have suggestions like, put project A and B and C together to
D, we should really discuss and consider it here. Because I agree that we can
reduce the number of projects.



Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >