Hi, Thanks for the precision even if it seems you have tools we know nothing about. But that's fine, if it is something you need, let's keep it that way. I will implement the functions i need trying to avoid code duplication.
Regards, On Fri, 2007-11-09 at 00:58 +0100, Erich Focht wrote: > Hi Geoffroy, > > the local repository is allways created because I want to enforce that there > is a local store for packages. I need this for packages which need to build > their kernel dependent part (for example blcr). > > Regards, > Erich > > On Thursday 08 November 2007 18:03, Geoffroy Vallee wrote: > > Hi, > > > > Thanks for this explanation. My next naive question will be: why this > > function, which is only supposed to list available repositories, does > > initialize some local only repository stuff in /tftpboot if nothing is > > in there? > > Because of the usage of online repositories, i would like this function > > (or another) to just give back an empty list; this allows one to choose > > how to setup the different repositories. In other terms, i am > > uncomfortable with the idea that this function always setup a local > > repository when it is supposed to list available repositories (local or > > online). > > > > Does it make sense for you? > > > > Regards, > > > > On Thu, 2007-11-08 at 10:12 +0100, Erich Focht wrote: > > > Hi, > > > > > > you are misunderstanding the fole of the function. > > > > > > list_distro_pools() returns a hash with primary key being all > > > distributions > > > that are configured to be supported in /tftpboot/distro. > > > > > > That means: > > > If a user wants to support centos-5-x86_64 (master+clients) and > > > centos-5-i386 (some clients), he should first make sure that yume has > > > access > > > to the corresponding distribution packages by: > > > > > > - copying all distro packages for centos-5-x86_64 to > > > /tftpboot/distro/centos-5-x86_64/ > > > > > > - copying all distro packages for centos-5-i386 to > > > /tftpboot/distro/centos-5-i386/ > > > > > > - creating /tftpboot/distro/centos-5-i386.url with the content: > > > file:/tftpboot/distro/centos-5-i386 > > > > > > - creating /tftpboot/distro/centos-5-x86_64.url with the content: > > > file:/tftpboot/distro/centos-5-x86_64 > > > > > > - alternatively: instead of copying in the distro packages one can add to > > > the .url files the URLs to base and updates repositories prefered. > > > > > > The approach with local distro files is allways working, and the > > > repository is > > > visible from clients in a non-routed cluster, too. The other approach > > > only works > > > if we configure a proxy on the master and point all clients to it, or if > > > the > > > clients have direct access to the outer world. > > > > > > > > > This means: a distro which a master can support must have a configured > > > distro repository. > > > > > > > > > Regards, > > > Erich > > > > > > > > > On Wednesday 07 November 2007 23:38, Geoffroy Vallee wrote: > > > > Hi, > > > > > > > > I try to update the new OPD in order to deal with repositories based on > > > > repositories definition in /tftpboot. For that i need to get the list of > > > > supported distros. I tried to use the function list_distro_pools from > > > > PackagePath but it seems that we currently assume that OSCAR > > > > repositories can ONLY be local. > > > > > > > > Is it normal? > > > > > > > > Regards, > > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
