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