2010/7/16 Colin Walters :
>
> But verifying a git tag is really easy too. I just disagree with you;
> if tarballs are provided, fine - if they aren't, it's trivial to use
> archives of git tags.
> --
Is there a script to help us to verify and pull sources from git repo?
Meego project have dozens
On Fri, Jul 16, 2010 at 6:26 AM, Chen Lei wrote:
>
> It seems no guideline forbid us to use tarballs extracted from
> upstream repo. I think using git repo for meego packages have more
> harm than benefit, because the most important feature for rpm is
> people can validate the md5sum of the sourc
2010/7/16 Mattias Ellert :
> fre 2010-07-16 klockan 18:26 +0800 skrev Chen Lei:
>
>> I think using git repo for meego packages have more
>> harm than benefit, because the most important feature for rpm is
>> people can validate the md5sum of the source tarball easily. Unless
>> special case we can'
fre 2010-07-16 klockan 18:26 +0800 skrev Chen Lei:
> I think using git repo for meego packages have more
> harm than benefit, because the most important feature for rpm is
> people can validate the md5sum of the source tarball easily. Unless
> special case we can't find a way to get reliable souce
2010/7/12 Kevin Kofler :
> Michel Alexandre Salim wrote:
>> I experienced this recently with another project (openSUSE's build
>> service client) -- GitHub lets you download a project's tagged
>> snapshots as tarballs, but Gitorious does not have this functionality.
>
> But on-demand autogenerated
2010/7/11 pbrobin...@gmail.com :
>
> I don't agree with the easier, and the releases are all built on tags.
>
> Well someone will have to get the policy added to the packaging
> guidelines. There's guidelines for using VC repos but not for using
> tar files from other distros source packages.
>
> P
Michel Alexandre Salim wrote:
> I experienced this recently with another project (openSUSE's build
> service client) -- GitHub lets you download a project's tagged
> snapshots as tarballs, but Gitorious does not have this functionality.
But on-demand autogenerated tarballs are evil because they us
On Sun, Jul 11, 2010 at 12:52 PM, Michel Alexandre Salim
wrote:
> On Sat, Jul 10, 2010 at 9:27 PM, Chen Lei wrote:
>> 2010/7/10 pbrobin...@gmail.com :
>>> Yes, but most of the Netbook side of things are from Moblin. Also if
>>> you look at a lot of the clutter/mx and other stuff they now do make
On Sat, Jul 10, 2010 at 9:27 PM, Chen Lei wrote:
> 2010/7/10 pbrobin...@gmail.com :
>> Yes, but most of the Netbook side of things are from Moblin. Also if
>> you look at a lot of the clutter/mx and other stuff they now do make
>> tarballs and in some cases only in the last weeks. Don't rule it ou
2010/7/10 pbrobin...@gmail.com :
> On Fri, Jul 9, 2010 at 5:28 PM, Chen Lei wrote:
>> 2010/7/9 pbrobin...@gmail.com :
>>
>>
>> I think it's not easy to persuade upstream to do so. Look deep at
>> meego-panel-zones, the HEAD version in git repo is 0.2.0[1], however
>> upstream rpm indicates the las
On Fri, Jul 9, 2010 at 2:21 PM, Chen Lei wrote:
> 2010/7/9 pbrobin...@gmail.com :
>> Hi Chen,
>>
>> As I'm the MeeGo maintainer let me outline my thoughts and reasoning
>> behind my MeeGo strategy.
>>
>>> I intend to review two meego-related packages[1][2], but I'm confused
>>> with which package
2010/7/9 pbrobin...@gmail.com :
> Hi Chen,
>
> As I'm the MeeGo maintainer let me outline my thoughts and reasoning
> behind my MeeGo strategy.
>
>> I intend to review two meego-related packages[1][2], but I'm confused
>> with which package name will be more appropiate.
>> [1]https://bugzilla.redha
Hi Chen,
As I'm the MeeGo maintainer let me outline my thoughts and reasoning
behind my MeeGo strategy.
> I intend to review two meego-related packages[1][2], but I'm confused
> with which package name will be more appropiate.
> [1]https://bugzilla.redhat.com/show_bug.cgi?id=610794
> [2]https://b
Hi Chen,
As I'm the MeeGo maintainer let me outline my thoughts and reasoning
behind my MeeGo strategy.
> I intend to review two meego-related packages[1][2], but I'm confused
> with which package name will be more appropiate.
> [1]https://bugzilla.redhat.com/show_bug.cgi?id=610794
> [2]https://b
14 matches
Mail list logo
