Re: [opensuse-factory] Zypper and dependent repos.

On 11/17/2011 04:44 PM, Greg Freemyer wrote:

On Thu, Nov 17, 2011 at 10:16 AM, Greg KH wrote:

...

...

So why does the main 12.1 repo not simply feed the TW repo?

That is exactly what it does, to build it against, not to actually provide it for users to sync against, that is now how Tumbleweed has ever worked.

I don't think zypper has the ability to automatically pull in dependent repositories.

I don't think it should be used often, but for the normal updates repo, tumbleweed, a maybe a couple others it would be great if zypper allowed a single repo to be added which in turn caused the underlying repo to be searched.

Thus if a user has the tumbleweed repo, there could be config data that tells zypper that it should also consider the opensuse_current repo to be part of it.

That way Greg KH could also control how the updates repo gets handled, etc.

Anyway, I'm not a zypper internals expert, so I'm just asking if this would be feasible.

Greg

You can do that if you implement the logic on the server side or as a client plugin: http://doc.opensuse.org/projects/libzypp/HEAD/zypp-services.html SLE works this way. You are not subscribed to a SLE repo but to a SLE service, which depending on the customer id, entitlements, etc, get a calculated list of repositories. What you describe is mentioned in the usecases section of the docs. -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org