On Tue, Dec 14, 2010 at 09:37:34AM +0100, Vincent Untz wrote:
Le lundi 13 décembre 2010, à 15:23 -0800, Greg KH a écrit :
On Fri, Dec 10, 2010 at 09:57:44AM +0100, Vincent Untz wrote:
Hi Greg,
Le jeudi 09 décembre 2010, à 10:01 -0800, Greg KH a écrit :
Hi all,
The openSUSE:Tumbleweed repo is now up and has exactly one package that will install properly, git. :)
Jiri is working on getting the kernel packages building properly, and I'm looking at linking to network:samba:STABLE as that's a good place to get the latest stable samba packages.
But, what I need from you all, is a request for what packages do you feel I should be updating right now, and hopefully you can provide a pointer to the repo for where these packages are (if they are only in FACTORY, that's fine as well.)
Can you elaborate on how Tumbleweed is managed? As far as I can see, you're making links to other projects (and, eek, git is a link to a home project -- that's something that should be avoided, imho: never link to home projects).
Why not? I trust the home project to have the proper version of that package. Would you like it better if somehow I just link to the Factory version instead? I trust the home project more as I know it builds and works properly on the 11.3 base, not just Factory.
You trust this specific home project because you know the person behind it. Will you trust other home projects if you don't know the people? Will other people trust this specific home project if they don't know the maintainer?
The question is really: do we want to trust all users on the build service?
No I do not, and yes, you are right, I am taking the package from Takashi because I trust him. Development is always a web of trust, that's how we as humans operate.
My understanding was that you wanted to use a model like the Factory one, where we push things to Tumbleweed when they are ready. But with links, that works a bit differently: (assuming we add some apps stuff from GNOME:Apps) when we update a package in GNOME:Apps, there's no hard guarantee it will work. We try to make that guarantee when we push from GNOME:Apps to Factory. I thought it'd be the same for Tumbleweed, but if it works with links, there's no way to make that guarantee.
Why not, these are just "links" of a copy type, not a link that instantly propagates.
i.e. I'm linking to a specific revision of the package, which should be fine, right?
Except that if the package you link to is deleted, it breaks. If the package moves somewhere else, it breaks. If someone decides to just force-rebranch the package (because it's easier than to revert some broken changes), it breaks.
Then we shouldn't like to packages that are likely to be deleted :) I would prefer to just accept submitrequests, but I know that some developers are a bit too busy for this so for that, I'm doing a link to handle the work for them.
In all cases, you can add all of GNOME:STABLE:2.32, I guess. If you use links, though, we will have to remember to change the links for a new GNOME version (since we'll likely use GNOME:STABLE:3.0 for the next version, etc.)
What do you think the proper management model for Tumbleweed would be to make your life as a package mantainer easier? In the end, I want to make it easiest for you, not me as a project manager.
For me? I'd just want it to be managed exactly like Factory :-) I submit changes when they are ready, they get accepted every once in a while. If we don't have a team to review those submissions, I could even just auto-accept my submissions. But at least, this way, I don't have to use two different processes for my two targets (Factory and Tumbleweed).
Wonderful, I would like to handle it this way as well. Care to send me a submitrequest for GNOME:STABLE:2.32 to be added to Tumbleweed? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org