[opensuse-buildservice] Buildservice and multiple repositories
Hi, I already wrote a mail about this topic, but as I read the same in a heise forum yesterday I try again. The usage of the BuildService is very complicated for the end user, as multiple repositories need to be added to get a recent installation. My suggestions would be to add a typo of meta repository, where the packes are only stored, but cannot be built. - You have a meta repository, which has no built feature - Packages are either imported into it or exported from the original repositories. - Conflicts are not resolved, but only marked in the original and the meta package. - Adding packages should be easy. Reason: Some all-in-one packages without the PacMan problems. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, May 10, 2007 at 08:26:49AM +0200, Dirk Stoecker wrote:
I already wrote a mail about this topic, but as I read the same in a heise forum yesterday I try again.
The usage of the BuildService is very complicated for the end user, as multiple repositories need to be added to get a recent installation.
Actually I'd rather have better support for multiple repositories in the installation tools. The mirror operators will not be happy if we have lots of repositories with identical rpms.
My suggestions would be to add a typo of meta repository, where the packes are only stored, but cannot be built. - You have a meta repository, which has no built feature - Packages are either imported into it or exported from the original repositories. - Conflicts are not resolved, but only marked in the original and the meta package. - Adding packages should be easy.
Reason: Some all-in-one packages without the PacMan problems.
You can actually already do that with aggregates, but as I said, please think of the mirrors... 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
On Thu, 10 May 2007, Michael Schroeder wrote:
On Thu, May 10, 2007 at 08:26:49AM +0200, Dirk Stoecker wrote:
I already wrote a mail about this topic, but as I read the same in a heise forum yesterday I try again.
The usage of the BuildService is very complicated for the end user, as multiple repositories need to be added to get a recent installation.
Actually I'd rather have better support for multiple repositories in the installation tools. The mirror operators will not be happy if we have lots of repositories with identical rpms.
Well, as this would be anyway a type of link, it could use softlinks in the repositories. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dirk Stoecker wrote: [...]
The usage of the BuildService is very complicated for the end user, as multiple repositories need to be added to get a recent installation.
No it isn't. It's rather that adding repositories is too complicated for some of the end users. Some ideas (and even code) are being developed on that topic atm. Skim through the opensuse-project archives for more information.
My suggestions would be to add a typo of meta repository, where the packes are only stored, but cannot be built. [...] - Conflicts are not resolved, but only marked in the original and the meta package.
What "meta package" ?
- Adding packages should be easy.
So, how do you decide what packages go into that "meta repository" and which not ? Only stable stuff ? How do you keep track of what's "stable" and what not ? Is the latest apache2 stable enough ? the latest xorg ? the latest KDE application packages ? etc... Or put *all* the packages of the build service into that "meta repository" ? No way, no realistic option IMO.
Reason: Some all-in-one packages without the PacMan problems.
Ah, "the PacMan problems".. what problems ?
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Thu, 10 May 2007, Pascal Bleser wrote:
The usage of the BuildService is very complicated for the end user, as multiple repositories need to be added to get a recent installation.
No it isn't. It's rather that adding repositories is too complicated for some of the end users.
The fact remains, that having 10-30 repositories is a large overhead. Even when the updating of these will be 5 times faster than for 10.2 it still will be awfully slow.
Some ideas (and even code) are being developed on that topic atm. Skim through the opensuse-project archives for more information.
I know. I'm not so sure if these will solve the problem, that I as users want to have one source for my OS. Accepting some exceptions is acceptable, but accepting lots of exceptions is a pain. I'm administering about 15 systems of different types using openSUSE and it's a real pain to get a recent system including all the stuff the users want to have (where the servers are the easiest parts). I wouldn't even let the users do anything like software installation. I'm complaining from a administrators point of view. I think if you would speak from my fathers users point of view my complainst would be much louder.
My suggestions would be to add a typo of meta repository, where the packes are only stored, but cannot be built. [...] - Conflicts are not resolved, but only marked in the original and the meta package.
What "meta package" ?
The package in the meta repository.
- Adding packages should be easy.
So, how do you decide what packages go into that "meta repository" and which not ? Only stable stuff ? How do you keep track of what's "stable" and what not ? Is the latest apache2 stable enough ? the latest xorg ? the latest KDE application packages ? etc...
The same way, as we do for the buildservice at all. If I have the right to write to meta-project named stableupdates and also can write and handle games:action, then I can link games:action/frozen-bubble to the meta project stableupdates. If not, I can't. If I can write to meta project "testversions" and have home:hubba/frozzen-bubble, then I can link it there. If not, I can't.
Or put *all* the packages of the build service into that "meta repository" ?
No way, no realistic option IMO.
That's why I did not suggest that.
Reason: Some all-in-one packages without the PacMan problems.
Ah, "the PacMan problems".. what problems ?
Go back into the archive of this mailing list: The problem of increasing package dependencies when projects include libraries. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 11 May 2007 09:25:50 wrote Dirk Stoecker:
On Thu, 10 May 2007, Pascal Bleser wrote:
The usage of the BuildService is very complicated for the end user, as multiple repositories need to be added to get a recent installation.
No it isn't. It's rather that adding repositories is too complicated for some of the end users.
The fact remains, that having 10-30 repositories is a large overhead. Even when the updating of these will be 5 times faster than for 10.2 it still will be awfully slow.
can you prove this somehow ? There shouldn't be any significant difference by parsing multiple small repos or one big (assume both have same content). bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N�rnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Adrian Schröter -
Dirk Stoecker -
Michael Schroeder -
Pascal Bleser