Mailinglist Archive: zypp-devel (149 mails)
| < Previous | Next > |
[zypp-devel] repository 'path'
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Thu, 11 Sep 2008 11:41:39 +0200
- Message-id: <48C8E7D3.3040800@xxxxxxx>
Hi Hackers,
the support for *path* in repositories (the piece appended to baseurl) is still not perfect in libzypp. I am about to fix it, but first i've got a few questions.
- DO WE NEED THIS AT ALL? :O)
AFAICT, we needed this for multi-product media (like patch-CDs
probably). I'm not sure why, though, can't we just go about it with
two different URLs? If some 'conent' file references the other
repo with a relative path, it should be no problem for libzypp to
just use the baseurl+this_path, no need to treat them separately(?).
Is the 'path' part of YUM's definition?
If your answer to these is 'NO,YES,NO', i'll be happy to remove all
the path stuff from libzypp now instead of fixing it for no good
reason :O) (maybe with some backward compatibility, reading the path,
and appending it to baseurls). And forget the next question then.
- our repository definition allows multiple baseurls to be defined, as
well as mirrors (these are ignored currently IIRC). What to do with
this:
[foorepo]
baseurl = http://url1.org/repos
baseurl = http://url2.org/whatever
path = foorepo/openSUSE/11.1
not to mention mirrors. Should we just use the path for all of the
baseurls?
cheers,
jano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
the support for *path* in repositories (the piece appended to baseurl) is still not perfect in libzypp. I am about to fix it, but first i've got a few questions.
- DO WE NEED THIS AT ALL? :O)
AFAICT, we needed this for multi-product media (like patch-CDs
probably). I'm not sure why, though, can't we just go about it with
two different URLs? If some 'conent' file references the other
repo with a relative path, it should be no problem for libzypp to
just use the baseurl+this_path, no need to treat them separately(?).
Is the 'path' part of YUM's definition?
If your answer to these is 'NO,YES,NO', i'll be happy to remove all
the path stuff from libzypp now instead of fixing it for no good
reason :O) (maybe with some backward compatibility, reading the path,
and appending it to baseurls). And forget the next question then.
- our repository definition allows multiple baseurls to be defined, as
well as mirrors (these are ignored currently IIRC). What to do with
this:
[foorepo]
baseurl = http://url1.org/repos
baseurl = http://url2.org/whatever
path = foorepo/openSUSE/11.1
not to mention mirrors. Should we just use the path for all of the
baseurls?
cheers,
jano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |