On Wed, Jan 14, 2009 at 01:15:12PM +0100, Lukas Ocilka wrote:
Benji Weber wrote:
2009/1/13 Duncan Mac-Vicar Prett
: A solution worth to explore is to start using variables like $releasever in the .repo files.
So repos with 11.1 would automaitcally be 11.2 afterwards. Of course still there is the need to check that those repos are valid.
Another possibility would be on upgrade to check for a file in each repository that would provide the URI of the equivalent repository in the new distro version.
That would require to initialize the repository at first and then download an optional file from there, then delete the repository again and register a new one provided by that file.
Funny how simple things have become. I thought it would be as complicated as one HTTP GET :-( HTTP::Get("myurl", Directory::tmpdir + "/myurl.out"); // (yast2-transfer)
Which also means we would have to setup the network before all this. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org