> >>> And lastly, why are you putting a separate meego.spec and > meego.yaml in a > >>> meego dir? what is this being used for? thanks in advance for the > info... > >>> > >>> > >> I can answer this. We currently have both debian packaging and MeeGo > >> packaging maintained in the master branch in the git repo for the > >> package. I know this is not an ideal situation, and it will likely > >> change as per the suggestion by Didier Raboud. But for now the > debian > >> and rpm packaging stuff is part of the upstream tar ball by > definition > >> (we are the upstream and we put it there). > > Thanks for your reply... > > So why are the .spec and .yaml files called > meegotouch-prestartd.spec/.yaml/.changes ? > > They also don't match the contents of the .spec, .yaml, or .changes > file in > the top-level dir...
Why does it matter if Pertti ships some packaging materials inside his upstream source tarball? The spec/yaml/changes that MeeGo should care is the files used to build the package in OBS. Cheers, Fathi _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
