[meego-packaging] autospectacle

[Alexander Kanevskiy]

On Tue, Aug 3, 2010 at 11:39, Anas Nashif <nashif at linux.intel.com> wrote:
>
> On 2010-08-03, at 8:02 AM, <fathi.boudra at nokia.com> <fathi.boudra at nokia.com> wrote:
>
>>> This needs to be fixed then. We don't accept anything but proper
>>> tarballs in the MeeGo repo.
>>
>> Links, please.
>> If it isn't written in MeeGo packaging guidelines, it doesn't exist.
>>
>>> No, a `git url + tag` does not constitute a release.
>>
>> In a perfect world, we have release tarball and use only released software, etc...
>>
>> The reality is:
>> - we ship package without a proper release tarball
>>  (in that case, upstream should be educated)
>> - we ship git or svn snapshots
>>  (in that case, it seems the maintainer responsability)
>>
>> IMHO, we should require a reproducible way to create the upstream tarball.
>> ie: git archive from a tag is fine.
>
> Yes, usually that is what we call a release. But someone picking a random state of a git repo is a NO GO.
> The standard way of doing this is to take last known release and apply patches ( diff last tag to head) and then merge back when there is a new release.

Anas, tag is not a "random state". it's a tag for release, and the
only thing that we need to do in case of having reproducible tarballs
is something like pristine-tar tool, so anybody can get the same
tar.{gz,bz2} with the same checksum everywhere.

> Anas
>
>>
>> Cheers,
>>
>> Fathi
>>
>> _______________________________________________
>> MeeGo-packaging mailing list
>> MeeGo-packaging at meego.com
>> http://lists.meego.com/listinfo/meego-packaging
>
> _______________________________________________
> MeeGo-packaging mailing list
> MeeGo-packaging at meego.com
> http://lists.meego.com/listinfo/meego-packaging
>



-- 
br, Alexander Kanevskiy