edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Karl Dahlke <eklhad@comcast.net>,  Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] 3.5.3
Date: Sat, 07 Feb 2015 09:32:01 -0800	[thread overview]
Message-ID: <87bnl5r5ke.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150207162404.GA26357@toaster.adamthompson.me.uk> (Adam Thompson's message of "Sat, 7 Feb 2015 16:24:04 +0000")

Adam Thompson <arthompson1990@gmail.com> writes:

> not least that it'll make version sorting (and version dependant package
> managers) behave correctly (git sorts before release in sorting)
> whereas 3.5.3 would probably sort *before* 3.5.3.git.

I've been a distro packager for many years.  If distros want to make
experimental packages, then there are various ways to do that, and it all
depends on the distro's package building machinery and policies.
It can also be kind of frustrating.
Using something like 3.5.3.git as a version string in a
distro package manager is probably not the best approach, either, since
the code in git is a moving target.  So my instincts as a distro
packager tell me to let the distros worry about how to package
experimental code, since policies and machinery aren't standard.

-- Chris

  reply	other threads:[~2015-02-07 17:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 22:48 Karl Dahlke
2015-02-07 16:24 ` Adam Thompson
2015-02-07 17:32   ` Chris Brannon [this message]
2015-02-07 16:34 ` Chris Brannon
2015-02-07 16:40 Karl Dahlke
2015-02-07 18:07 ` Adam Thompson
2015-02-09 14:07 Chris Brannon
2015-02-09 14:17 ` Adam Thompson
2015-02-09 14:26 Karl Dahlke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bnl5r5ke.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).