On Mon, Jun 25, 2007 at 08:16:05PM +1000, John Pye wrote:
Michael Schroeder wrote:
On Sat, Jun 23, 2007 at 10:09:11PM +1000, John Pye wrote:
There is a SCons package somewhere else in the Build Service and I can link to that if I want.
That's probably the wrong approach, instead you should layer the repositories in question on top of the ones containing the SCons package.
Firstly, how would I do that?
Via the "Expert" mode in the repository creation dialog.
And what is the implication for my 'home:jdpipe' repository in that case?
That's a project, not a repository. The repository search path can be configured individually for every repository in your project.
Does it gain all of the other repository's packages somehow?
No, it just uses the packages for building.
Or do I need to tell users to add *two* files to their yum.repos.d folder instead of one?
I'm afraid this is true for the current installers. If you don't want this, you can use an "aggregate" to copy some binary packages into your repository without the build step. (A link just links the sources, so every linked package needs to be rebuilt.)
And I wonder why in this case it's not better to just selectively build the package for those distros that lack it.
Or aggregate them.
Actually: it would be great if one could somehow automatically specify only to build certain packages when the package is not in the source repository, eg a special comment in my spec file: # NotRequiredIf: scons >= 0.96.92
Hmm, I have to think about this a bit. 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