On Thu, Aug 30, 2012 at 10:59 PM, Andreas Jaeger <aj@suse.com> wrote:
What exactly is not clear?
Maybe he wants to know what kind of package go to what kind of devel repository. That's the place where we ignore in documentation. Actually a "devel projects list" with detail explanations is a must. or it'll be a mystery to OBS freshman. eg 1: Arch:core if you know there's a distribution named ArchLinux, and you know OBS supports it. You'll know it's a link project to all of core prebuilt packages from Archlinux. But what if you not? you might think it to be a "Architecture Core" devel repository. So you submit all your x86_64 and i586 packages against it. then what will happen? no one answers you at all...because seems there're no maintainers for that repo. Only Adrian knows there's a SR against it. Acutally not all devel projects start with "devel:", there'are exceptions like "editors". But not all projects without "devel" are not devel projects either. And not all projects start with "devel" are devel projects, for example "devel:perl:CPAN:A-N". eg 2: KDE:Extra Can you judge what this is according to its name? Apparently not. If you think it is a KDE Extra repository, okay, you're wrong. Actually it's KDE Extra repository which can not be used to SR to Factory. I miss SR many requests into it. But what if KDE:Distro:Factory? Actually it much like a standard suite of KDE for Factory. If you submit some extragear into it. well, it feels embarrassing. We have so many repositories. That's good. but one person can only focus on a few of them. But which one should he focus on at the beginning? no one knows. So we'd better have a wiki page called "OBS repositories layout" to catalog and explain them. This is good for both packagers and maintainers to get an overview. Marguerite -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org