[softwaremgmt] .repo files
We are designing the new repo handling model of the SUSE package manager stack to be more compatible with YUM, smart and the build service .repo files. When I looked at the .repo files at the first time, I thought the baseurl= was a unique url, which was the url of the origin of the metadata (used to identify), and the actual urls were pulled from a mirror list. I was confused for a bit when I discovered a .repo can have more than one baseurl. Even more when saw the strange way to do multi-line in the ini file. That means basically, there is no url you can use to, in the case you add a .repo file which has a list of urls, but the same base url as an already existing .repo, just append the urls to the mirrorlist. Ok, that sucks (as much as the documentation). But now comes another problem. Our (broken) model, requires a pair (url, path). If we support more than one baseurl in the .repo file, you can't have path as a separate unique attribute. .repo files doesn't specifiy path. I think the best solution is to get rid of path completely. Do we need it? no. It is needed in CD, NFS only (probably ISO too?) because we are using it in a wrong way. Can aynone give examples? why is needed? I am sure we can destroy those examples using the standard Url structure (and abusing options) Duncan -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Dňa Št 31. Máj 2007 17:08 Duncan Mac-Vicar Prett napísal:
We are designing the new repo handling model of the SUSE package manager stack to be more compatible with YUM, smart and the build service .repo files.
When I looked at the .repo files at the first time, I thought the baseurl= was a unique url, which was the url of the origin of the metadata (used to identify), and the actual urls were pulled from a mirror list. I was confused for a bit when I discovered a .repo can have more than one baseurl. Even more when saw the strange way to do multi-line in the ini file.
That means basically, there is no url you can use to, in the case you add a .repo file which has a list of urls, but the same base url as an already existing .repo, just append the urls to the mirrorlist.
Ok, that sucks (as much as the documentation). But now comes another problem.
Our (broken) model, requires a pair (url, path). If we support more than one baseurl in the .repo file, you can't have path as a separate unique attribute. .repo files doesn't specifiy path. I think the best solution is to get rid of path completely. Do we need it? no. It is needed in CD, NFS only (probably ISO too?) because we are using it in a wrong way.
Can aynone give examples? why is needed?
Path is used for YaST sources (our installation media), which can contain multiple products. In this case, you split the URL for managing multi-media installation sources. Stano -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
On Monday 04 June 2007 13:12:57 Stanislav Visnovsky wrote:
Path is used for YaST sources (our installation media), which can contain multiple products. In this case, you split the URL for managing multi-media installation sources.
Stano
Can you give an example? -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
Dňa Po 4. Jún 2007 13:33 Duncan Mac-Vicar Prett napísal:
On Monday 04 June 2007 13:12:57 Stanislav Visnovsky wrote:
Path is used for YaST sources (our installation media), which can contain multiple products. In this case, you split the URL for managing multi-media installation sources.
Stano
Can you give an example?
Actually no, I'm not aware of any real usage of the semantics except for base product (openSUSE). Stano -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
On Thu, Jun 07, Stanislav Visnovsky wrote:
D??a Po 4. J??n 2007 13:33 Duncan Mac-Vicar Prett nap??sal:
On Monday 04 June 2007 13:12:57 Stanislav Visnovsky wrote:
Path is used for YaST sources (our installation media), which can contain multiple products. In this case, you split the URL for managing multi-media installation sources.
Stano
Can you give an example?
Actually no, I'm not aware of any real usage of the semantics except for base product (openSUSE).
- The URL denotes the media (not the repository)! - If the media itself contains additional (non repository) data, e.g. /media.N/media to identify the individual CDs in a set, you must differ between media and repository (or you are limited to one repo per media located at /). The difference beween URL PATH cd:// /reporoot cd://reporoot / is not the location of the repository data. It's the e.g. expected location of the media.n/ directory. cd://media.n/ cd://reporoot/media.n/ I'm not shure whether the restriction (one repo per media located at /) is acceptable. If we want to store the repository url only, a solution for the media change callback could be simple: We do the media.n/media check in case of CD/DVD only (and not all the time, as we do now). We should always be able to access the dvd/cd root directory. Potential pitfalls (PATH != /): - Applications (YaST) may use the repositories URL to access files on the media, expecting it to denote the media root dir. - Copying a CD-set to disk - using directories CD1, CD2,... - will fail, because we check whether the URL ends in a number and replace it with the media number. (but that might be easy to fix by adapting the URL rewrite). -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
On Tuesday 12 June 2007 17:47, Michael Andres wrote:
The difference beween
URL PATH cd:// /reporoot cd://reporoot /
is not the location of the repository data. It's the e.g. expected location of the media.n/ directory.
cd://media.n/ cd://reporoot/media.n/
I'm not shure whether the restriction (one repo per media located at /) is acceptable.
Exactly, but the combination of url and path should then only used for a tool scanning a media for products, but not for a repository itself. Duncan -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
* Duncan Mac-Vicar Prett
Our (broken) model, requires a pair (url, path). If we support more than one baseurl in the .repo file, you can't have path as a separate unique attribute. .repo files doesn't specifiy path. I think the best solution is to get rid of path completely. Do we need it? no. It is needed in CD, NFS only (probably ISO too?) because we are using it in a wrong way.
For CDs, you probably even need more (i.e. the media id) to identify the CD unambiguously. A pure URL is fine for http(s) and ftp, but removable media needs additional identification data. It could be encoded in the url, though. Klaus -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
participants (5)
-
Duncan Mac-Vicar -
Duncan Mac-Vicar Prett
-
Klaus Kaempf -
Michael Andres -
Stanislav Visnovsky