Hello,
> > What I would suggest is to cache the oscar_repositories.xml into OPD. > > That way, when the repository definition file is not avalaible, the > > "old" one can be used and the packages will be avalaible even if the > > oscar.sf.net web site is down (an up to date version of this file at the > > time of each OSCAR release will be bundled with the regular OSCAR > > distro). > > Ahem. OPD actually does cache the file. :-) > > But you have to download it at least once to get that cache filled. Yep. > I do not think it is a good idea to include a copy of the repository file > in an OSCAR distribution. The whole point is that it is a dynamic list > and may change at any time. What I would like is a "very smart OPD" : just ask for the modification time and size of the oscar_repositories.xml files. If it is the same, don't download it and, if the file is not accessible, use your old file. In this context, you don't loose dynamism and you do not depend on the remote avalaibility of the oscar_repositories.xml. All in all, I think it only removes a dependency and doesn't diminish the dynamism of the repositories. Ben -- Benoit des Ligneris Ph. D. <|> http://benoit.des.ligneris.net/ Centre de Calcul Scientifique <|> http://ccs.USherbrooke.ca/ OSCAR Developpe(u)r <|> http://oscar.sourceforge.net/ �duLinux <|> http://www.edulinux.org/ R�volution Linux <|> http://www.revolutionlinux.com/ ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
