[Debian-ha-maintainers] libqb is ready
Richard B Winters
rik at mmogp.com
Mon Mar 30 21:51:06 UTC 2015
On Mon, 2015-03-30 at 22:34 +0100, Matthew Vernon wrote:
> Hi,
>
> > I don't understand cloning a repository and all of its history -> when
> > we are supposed to be packaging using the release tarball anyhow -> not
> > the commit used for the tarball release...no?
>
> It makes it easier to cherry-pick upstream commits and so on. The
> various git packaging tools let you say "this is the upstream tarball
> that corresponds to release X" and suchlike. It also helps you have a
> coherent history in your repo.
I get that it helps make it easier to cherry pick commits and patch the
source - where I felt there was contradiction was in stating I couldn't
manually prep the orig.tar.gz file -> yet am being advised to import a
repository rather than a tarball and allow git tools (or myself) to
manually prep the .orig.tar.gz file...
> > So is Github.com...did you mean to imply something other than this? I
> > only suggest using Github.com because of all the advanced features we
> > could be taking advantage of - which Alioth does not have.
>
> Alioth is free as in free software, github is not. So we should use
> alioth for Debian things (or other free software tools), not github.
>
> Regards,
>
> Matthew
>
Ah -
So since we can't get our hands on Github.com's source we shouldn't use
its free service for Debian? Yet we'll gladly import an upstream
repository from Github.com and put a watch file looking at Github.com
into our packages?...I don't really get it - we're not packaging
Github.com, but source obtained from it - yet being the newbie here I
will not argue it -> will scratch the Github.com repo and only use
Alioth for our packages then.
Thanks for the reply Matthew :)
Best,
--
Rik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/debian-ha-maintainers/attachments/20150330/51ccbecd/attachment-0001.sig>
More information about the Debian-ha-maintainers
mailing list