----- Original Message -----
> On Fri, Aug 12, 2011 at 2:32 AM, Nasa <[email protected]> wrote:
> >
> > > Rudi
> > >
> > Thanks Rudi,
> >
> > I will have to take a read.  I obviously didn't explain what I was
> > after
> > very well.  On the
> > https://build.pub.meego.com/project/add_repository_from_default_list?project=home%3Anasa
> > page there a list of repositories one can add (such as Meego 1.1,
> > 1.2, debian, etc),
> > however, there isn't one for some of the development tracks.  For my
> > interest, 1.2.0.90
> > (ie: future 1.2.1) is the repository I would like to build some
> > updated packages against.
> > I have already done it against Meego 1.2 and Current:Core.
> >
> > From your example, how was the repo for trunk added?  It's not
> > listed as a repo that can be
> > added...
> 
> You should be able to add various repos in the "advanced" tab on that
> same page, where it says: "Or pick one via advanced interface." There
> are a lot of distros to build against, I haven't seen the one you're
> after but I didn't go through the whole list. It isn't obvious, but
> that form is partial an auto-complete form. So start typing in the
> "project" field until you find the repo you want to build against.

Thanks Jeremiah,

I was putting in the name of my project in that field instead of 
other projects.  Once I did things like "meego" a whole lot more options
showed up...  However, I didn't see anything related to 1.2.0.90 and/or
1.3.  It looks like this field is only pulling from projects listed on pub
OBS - not the build one.  Is there a way to cross connect the two?

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.

Thanks for putting up with us old, slow men.

Nasa 


_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to