[meego-packaging] Figuring out which packages to require

[Arjan van de Ven]

On 7/28/2010 4:41 AM, Pertti Kellomäki wrote:
> On 07/28/2010 02:16 PM, ext Arjan van de Ven wrote:
>> wait... are you storing the yaml/spec files inside your upstream release
>> tarbal?????
> The yaml file is in the same git repo in gitorious as the sources: 
> <http://meego.gitorious.org/meegotouch/meegotouch-applifed>. What I do 
> is I clone the repo, create the tarball with `git archive' for the 
> desired tag, and run specify on meegotouch-applifed.yaml to get 
> meegotouch-applifed.spec.
>> that's... weird and likely not a good idea... I'd strongly suggest
>> considering to not do that, and keep packaging as part of the
>> distribution, and source code for the upstream tarbal
>> packaging is distribution specific..
> If you take a look at http://meego.gitorious.org/meegotouch/*, all the 
> projects have debian packaging files in $(TOPDIR)/debian, and some of 
> them (libmeegotouch for example) have the spec file in $(TOPDIR). Our 
> yaml file is in $(TOPDIR)/meego exactly because packaging is 
> distribution specific.
>
> Being both the upstream and the packager does muddy the waters, and I 
> would prefer the two roles to be separated. We are upstream by 
> definition, and we are a debian packager for harmattan, but now we 
> have been asked to be a MeeGo packager as well, so we stumble on the 
> best we can.

last time I stuck a debian/ directory in one of my upstream packages, I 
got a rather earful from the debian package maintainer that this was a 
mortal sin...