On Saturday 08 February 2014 09:01:46 Tzafrir Cohen wrote:
> On Fri, Feb 07, 2014 at 10:41:56AM -0600, Michael Shuler wrote:
> > On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
> > >Is there a policy on how to package software that does not make releases?
> >
> > A version similar to skia_0.0-1
]] Tzafrir Cohen
> Answering myself: here's a simpler trick:
>
> Subversion revisions:
>
> 0~svn
>
> Switching to git:
>
> 0.0~git
Why do you want to put the git/svn before the revision information?
0~20140209+svn1234
0~20140209+git$sha1
If you need more than one a day, you can do 0~201402
Another round of nitpicking:
On Sat, Feb 08, 2014 at 10:01:46AM +0100, Tzafrir Cohen wrote:
> On Fri, Feb 07, 2014 at 10:41:56AM -0600, Michael Shuler wrote:
> > On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
> > >Is there a policy on how to package software that does not make releases?
> >
>
On 02/08/2014 05:55 AM, Andreas Beckmann wrote:
On 2014-02-08 10:01, Tzafrir Cohen wrote:
On Fri, Feb 07, 2014 at 10:41:56AM -0600, Michael Shuler wrote:
On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
Is there a policy on how to package software that does not make releases?
A version sim
Quoting Tzafrir Cohen (2014-02-08 10:01:46)
> On Fri, Feb 07, 2014 at 10:41:56AM -0600, Michael Shuler wrote:
>> On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
>>>Is there a policy on how to package software that does not make
>>>releases?
>>
>> A version similar to skia_0.0-1~svnr1234 would a
On 2014-02-08 10:01, Tzafrir Cohen wrote:
> On Fri, Feb 07, 2014 at 10:41:56AM -0600, Michael Shuler wrote:
>> On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
>>> Is there a policy on how to package software that does not make releases?
>>
>> A version similar to skia_0.0-1~svnr1234 would allow
On Fri, Feb 07, 2014 at 10:41:56AM -0600, Michael Shuler wrote:
> On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
> >Is there a policy on how to package software that does not make releases?
>
> A version similar to skia_0.0-1~svnr1234 would allow an upstream
> version of i.e. 0.1 (if they ever
Pau Garcia i Quiles wrote:
>
>I am interested in packaging Skia ( https://code.google.com/p/skia/ ), the
>2D library used in Chromium, Firefox and others. I need it because a
>package I maintain (witty) is replacing GraphicsMagick with Skia.
>
>I went to Skia's download page and... found there is n
Quoting Pau Garcia i Quiles (2014-02-07 17:51:47)
> I have also noticed Firefox includes Skia in its source package,
> although it may be justified because they heavily patch Skia. Icedove
> (Thunderbird) and XULRunner also include their own version of Skia.
Thanks for noticing!
Please report t
My apologies if something isn't right with this email, I'm writing from my
phone.
> On 7.2.2014, at 18.25, Pau Garcia i Quiles wrote:
>
> Hello,
>
> I am interested in packaging Skia ( https://code.google.com/p/skia/ ), the 2D
> library used in Chromium, Firefox and others. I need it because
On Fri, Feb 7, 2014 at 5:52 PM, Andreas Beckmann wrote:
> If your upstream is git, you don't have monotonically increasing
> revision numbers, but (unordered) commit hashes. I usually use something
> based on 'git describe' as that gives you a number of commits since a
> reference tag in additio
Quoting Michael Shuler (2014-02-07 17:41:56)
> On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
> > Is there a policy on how to package software that does not make releases?
>
> A version similar to skia_0.0-1~svnr1234 would allow an upstream version
> of i.e. 0.1 (if they ever release) to supe
On 2014-02-07 17:25, Pau Garcia i Quiles wrote:
> Is there a policy on how to package software that does not make releases?
You usually make up your own upstream version number, either
revision-based or date-based or both. Just ensure you use a version that
sorts before any later upstream release.
On Fri, Feb 7, 2014 at 5:41 PM, Michael Shuler wrote:
> Is there a policy on how to package software that does not make releases?
>>
>
> A version similar to skia_0.0-1~svnr1234 would allow an upstream version
> of i.e. 0.1 (if they ever release) to supersede your packaged version. It
> should al
On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote:
Is there a policy on how to package software that does not make releases?
A version similar to skia_0.0-1~svnr1234 would allow an upstream version
of i.e. 0.1 (if they ever release) to supersede your packaged version.
It should also allow you
Hello,
I am interested in packaging Skia ( https://code.google.com/p/skia/ ), the
2D library used in Chromium, Firefox and others. I need it because a
package I maintain (witty) is replacing GraphicsMagick with Skia.
I went to Skia's download page and... found there is none: Skia does not
make re
16 matches
Mail list logo
