Archie Cobbs wrote:

So I think that the answer here is to create a "link" from another project (I read about _link vs. _aggregate but notice that this choice is not available via the web GUI so I don't worry about it).

Yes, there should be a GUI for aggregating packages.

I do a search for "js-devel" and find it listed under "OSSP/openSUSE_10.3".

So I try to create a link to my home project from original project="OSSP" and original package="js-devel".

Result: Unable to find package 'js-devel' in project 'OSSP'.

Links link package sources and 'js-devel' is a subpackage of the 'js' source package. BTW, to aggregate the js pacage, delete the _link file and create an _aggregate file instead: <aggregatelist> <aggregate project="OSSP"> <package>js</package> </aggregate> </aggregatelist> hth, Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Fri, May 2, 2008 at 3:08 PM, Archie Cobbs wrote:

Now I have another simple/dumb question...

More stupid questions... Now I've created an _aggregate link from project "XML/xml-10.3" package "Xerces-c" because I need "Xerces-c-devel" to build this voiceglue thing: <aggregatelist> <aggregate project="XML"> <package>Xerces-c</package> </aggregate> </aggregatelist> But my linked "Xerces-c" project is broken because: "missing repositories: XML/openSUSE_10.3". So then I tried doing this... <aggregatelist> <aggregate project="XML" repository="xml-10.3"> <package>Xerces-c</package> </aggregate> </aggregatelist> ...and this... <aggregatelist repository="xml-10.3"> <aggregate project="XML"> <package>Xerces-c</package> </aggregate> </aggregatelist> but it still breaks due to "bad aggregatelist data". I apologize for asking so many newbie questions... Thanks, -Archie -- Archie L. Cobbs --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Fri, May 2, 2008 at 5:26 PM, Marcus Hüwe wrote:

...

but it still breaks due to "bad aggregatelist data".

You have to map the repository names:

Thanks again for your help. I realize now that this is in the wiki page... and I had indeed read that before but didn't understand it the first time (not a good sign)... I think things would be a lot clearer to new people if there was a "big picture" wiki page. This would give clear definitions of "repository", "project", "link", etc. I still don't know exactly what those mean. For example, the documentation tells you how to "add a repository to a project" .. but what does that mean? I think I know what it means... you are simply allowing your build to pull in required RPMs from the other repository -- right? When and why would you ever create a new repository? What exactly does it mean to do so? Also, clear description of the various XML files and what exactly the XML tags and attributes mean. Also it would inform you that the labels in grey in the search page are in the form "project/repository". And having an RPM that requires one or more other RPMs that are not part of standard SuSE 10.3 is probably a common situation, so it would be helpful to describe how to handle that. I was under the mistaken impression that I needed to create links... but actually, "osc meta -e prj ..." and adding <path> tags is the right answer (right??). You get the idea... I hope my confusion can help improve the experience for future builders. I would be willing to document all this stuff myself except I still don't fully understand it yet. Thanks, -Archie -- Archie L. Cobbs --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org