public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: "andrew@ncrmnt.org" <andrew@ncrmnt.org>,
	"crossgcc@sourceware.org"	<crossgcc@sourceware.org>
Subject: Re: crosstool-NG Debian packaging
Date: Tue, 23 Feb 2016 21:15:00 -0000	[thread overview]
Message-ID: <38f32ea3273b4d4f932d86bbb1638fcc@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: <8D9280FC-7393-4B14-980E-F54BCE4EA959@gmail.com>

On 02/23/2016 05:40 PM, Bryan Hundven wrote:
> Chris,
>
>
>> On Feb 22, 2016, at 7:55 PM, Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
>>
>> On 02/11/2016 10:43 AM, andrew@ncrmnt.org wrote:
>>> 10 февраля 2016 г., 23:32, "Chris Packham" <Chris.Packham@alliedtelesis.co.nz> написал:
>>>> Hi Bryan, Andrew,
>>>>
>>>> I see that there is some movement on packaging crosstool-NG for Debian.
>>>> This is relevant to my interests and I have subscribed to your mailing
>>>> list :).
>>>>
>>>> Is there an open Debian bug for this? I've found a few older ones but
>>>> they all seem to have timed out due to lack of interest.
>>>
>>> Hi, Chris. Unfortunately, I'm not a debian maintainer and there's no open bug
>>> for that in debian bugtracker. I've done the packaging for my own needs,
>>> since it was waaay faster than opening a bug ;). So unless you know some debian
>>> maintainers crosstool-ng won't land in debian repositories any time soon;)
>>>
>>
>> So in a fit of optimism I thought I'd give submission to debian a go.
>> Based on Andrew's work I've got packaging for the released 1.22.0 with
>> some patches I need for my own selfish needs.
>>
>> Andrew are you happy to be listed in the debian/control as the
>> maintainer or do you want me to put my name in there instead (or should
>> I put Bryan).
>>
>> I also notice that the tarball from github[1] has some unfortunate paths
>> in it, "crosstool-ng-crosstool-ng-1.22.0" which makes packaging it a bit
>> of a pain (1.21.0 also seems to have the same issue).
>>
>> Is there any way we can get that fixed? I have re-generated the tarball
>> locally but if someone were to compare the md5sum of my tarball to the
>> one from github they might think something malicious was going on.
>>
>> Thanks,
>> Chris
>> --
>> [1] -
>> https://github.com/crosstool-ng/crosstool-ng/archive/crosstool-ng-1.22.0.tar.gz
>
> Also, it is recommended to use the source release here:
>
> http://crosstool-ng.org/download/crosstool-ng/crosstool-ng-1.22.0.tar.bz2
>
> As this version has autoconf ran, and is PGP/GPG signed.
> http://crosstool-ng.org/#download_and_usage
>

Annoyingly (from a debian packaging point of view) that has a different 
issue. It doesn't include the -1.22.0 part in the path. But that fact 
that it's signed probably does make it better than either getting it 
from github or me re-generating it.

I'll see if I can convince debuild not to complain about the paths.

How do you actually generate the releases? I don't see a "make dist" 
target after running ./bootstrap && ./configure. I'm unsure how you 
actually tell automake not to include a "dist" target so maybe something 
is missing (or it's intentional in which case I'll shut up).

> Cheers,
>
> -Bryan
>


--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2016-02-23 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 20:32 Chris Packham
2016-02-10 20:41 ` Bryan Hundven
2016-02-10 20:49   ` Chris Packham
2016-02-10 20:52     ` Bryan Hundven
2016-02-10 21:05       ` Chris Packham
2016-02-10 21:43 ` andrew
2016-02-23  3:55   ` Chris Packham
2016-02-23  4:37     ` Bryan Hundven
2016-02-23  4:40     ` Bryan Hundven
2016-02-23 21:15       ` Chris Packham [this message]
2016-02-23 13:05     ` Thomas Petazzoni
2016-02-23 15:41       ` Bryan Hundven
2016-02-23 21:26         ` Github tags (was Re: crosstool-NG Debian packaging) Chris Packham
2016-02-12  4:20 ` crosstool-NG Debian packaging Chris Packham
2016-02-12 19:49   ` Bryan Hundven
2016-02-14 19:42     ` Chris Packham

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=38f32ea3273b4d4f932d86bbb1638fcc@svr-chch-ex1.atlnz.lc \
    --to=chris.packham@alliedtelesis.co.nz \
    --cc=andrew@ncrmnt.org \
    --cc=bryanhundven@gmail.com \
    --cc=crossgcc@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).