So... I thought I understood what repo actually went to what path (ie: MeeGo.Com seems to go to the build.meego.com) but now I know I don't get it. I have added a repo called Meego:Trunk/standard, which I thought actually was download.meego.com/live/trunk/standard. It's not... Using a .ks that identifies the afore mentioned directory, I am getting some slightly different packages availability (gpsd 2.96 in the one I linked to 2.37 for the Meego:Trunk/standard).
So back to the original question, how do I tell what path matches the repo listed on the pub OBS. BTW, a repo added from MeeGo.com won't be built against. Even though I can branch packages off of it. Nasa ----- Original Message ----- > On 08/12/2011 06:44 AM, Nasa wrote: > > > > ----- Original Message ----- > > The one thing that I am still confused on... When I add a repository > > I assume > > I am building against a list of packages included in said repo. But > > I don't > > see a way to see what packages are actually included in the repo I > > may have > > just added. > I think the best way is to check the repository link of said project. > > Regards, > _______________________________________________ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev > http://wiki.meego.com/Mailing_list_guidelines _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
