<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Dominique Leuenberger wrote:
<blockquote cite="mids5589b26.051@mail.TMF-Group.com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2800.1400" name="GENERATOR">
<div> <br>
<br>
>>> Reply on 13-11-2006 17:12:44 <<<> On Mon,
2006-11-13 at 15:58 +0100, Dominique Leuenberger wrote:<br>
> <br>
> There's no irc channel, no, but I'm not sure there's much to meet<br>
> about.<br>
> The feature you're asking for doesn't make any sense to me. We're<br>
> talking about adding a significant amount changes to the backend
to tie<br>
> repositories together in order to facilitate just adding a .repo
file<br>
> in /etc/yum.repos.d/<br>
> <br>
> That seems handling the problem the wrong way, imo.<br>
> <br>
</div>
<div>Hmm, as I said, it's not only for this particular project that I
ask, I'm more here as a dellegate.</div>
<div>The change would be to extend the .repo format to support
something like</div>
<div> </div>
<div>[channelName]</div>
<div>name=A sample repository</div>
<div>type=rpm-md</div>
<div>baseurl=<a class="moz-txt-link-freetext" href="http://..../BinaryRepo/OS/Version">http://..../BinaryRepo/OS/Version</a></div>
<div>gpgcheck=1</div>
<div>gpgkey=.....</div>
<div>enabled=1</div>
<div>dep-baseurl=<a class="moz-txt-link-freetext" href="http://..../DataRepo/">http://..../DataRepo/</a></div>
<div>dep-gpgcheck=1</div>
<div>dep-gpgkey=......</div>
<div>(optionally multiple dependencies, but that is probably nothing
that should be needed)</div>
<div> </div>
<div>So, the new part would be dep-* which would instruct to link in
at least on more repo.</div>
<div> </div>
<div>What other solution can you see? Of course, the user can add 2
repos, but that's a thing more or less impossible to instruct all users.</div>
<div> </div>
<div>The important part would be to have the SPEC for this .repo file
set to a new version. Of course at the beginning not all binaries will
interpret them (but they are hopefully kinda grateful on unknown
parameters)</div>
<div> </div>
<div>so: you think there's really nothing that can be discussed about
such a feature request anymore?</div>
<div> </div>
<div>Dominique</div>
</blockquote>
This don't make any sense to me:<br>
<br>
You can define more repositories in the same repo file.<br>
<br>
<div>[channelName]</div>
<div>name=A sample repository</div>
<div>baseurl=<a class="moz-txt-link-freetext" href="http://..../BinaryRepo/OS/Version">http://..../BinaryRepo/OS/Version</a></div>
<div>gpgcheck=1</div>
<div>gpgkey=.....</div>
<div>enabled=1<br>
<br>
<div>[channelName-data]</div>
<div>name=A sample data repository</div>
<div>baseurl=<a class="moz-txt-link-freetext" href="http://..../DataRepo/">http://..../DataRepo/</a></div>
<div>gpgcheck=1</div>
<div>gpgkey=.....</div>
<div>enabled=1</div>
</div>
<br>
You can build an rpm containing the repo files, this seem like a repo
file distribution problem, it don't need any changes<br>
in yum.<br>
I the Fedora world there is a lot of 3.part repositories not included
in the base repo setup, most for them have create an<br>
rpm file with the repofiles, gpg keys etc. to setup the repository
configuration.<br>
The user just download and install the rpm file and the 3. part repo is
added.<br>
<br>
Tim<br>
<br>
<br>
</body>
</html>