Santtu Lakkala <[EMAIL PROTECTED]> writes: > I have targets for mistral/2.0 (to support mistral, scirocco and > gregale), bora/3.0 (to support bora 3.0, 3.1, 3.2) and now chinook-beta > to support the upcoming N810. I then compile packages first on mistral > and see if they work on bora -- if they don't, rebuild with bora...
Thanks; together with your recent blog post that contains the details of how to set this up, that is exactly what I was looking for. > I didn't find documentation for chinook .install files, but reading the > source, I got the following: > > ----8<----8<----8<---- > [install] > package = <package to be installed> > catalogues = <comma separated list of repositories for the package> > > [<repository1>] > name = <repository name> > uri = <base uri> > dist = <dist name> > components = <components> > ----8<----8<----8<---- > > Of course the .install file can still include the repo_name, repo_deb > and repo_deb_3. For example, mh-shot-tool install file currently looks > like this: > > ----8<----8<----8<---- > [install] > repo_name = maemo-hackers > catalogues = maemo-hackers-chinook > repo_deb = deb http://maemo-hackers.org/apt mistral main > repo_deb_3 = deb http://maemo-hackers.org/apt bora main > package = mh-shot-tool > > [maemo-hackers-chinook] > name=Maemo Hackers for chinook > uri=http://maemo-hackers.org/apt > dist=chinook > components=main > ----8<----8<----8<---- Fantastic, thanks. Neil _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
