From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Geert Stappers <stappers@stappers.nl>,
Alexis Murzeau <amubtdx@outlook.fr>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>,
"721430@bugs.debian.org" <721430@bugs.debian.org>
Subject: Re: Bug#721430: crosstool-ng packaging for Debian
Date: Mon, 24 Jul 2017 00:32:00 -0000 [thread overview]
Message-ID: <6f770e81f1e94de6afb9b7daae4bf763@svr-chch-ex1.atlnz.lc> (raw)
In-Reply-To: <20170718195751.GI21385@gpm.stappers.nl>
On 19/07/17 07:57, Geert Stappers wrote:
> On Mon, Jul 17, 2017 at 09:26:53PM +0000, Alexis Murzeau wrote:
>> On 17/07/2017 17:44, Geert Stappers wrote:
>>>
>>>> using existing work.
>>> Most likely you missed some of the existing work.
>>> We, Chris, you (Alexis Murzeau) and I (Geert),
>>> need to find out what work exists and merge it in one.
>>>
>>> What is needed that some of us says:
>>> URL is for the time being the leading SCM repository
>>>
>>
>> I've found so far only the main repository on github at [1] to contains
>> Debian packaging files.
>> I've not checked the package on mentors.debian.net extensively but found
>> it relatively close to the one in official sources [1].
>> I can't find the crosstool-ng package on mentors.debian.net anymore,
>> does it get to a new stage ?
>>
>>
>> Is there other already known repositories out there ?
>
> git repro https://github.com/cpackham/crosstool-ng.git
> branch debian-packaging-update
>
The changes from that branch have been merged to the upstream repo so
it's effectively dead. I'll probably delete it shortly.
>> (So I can maybe make a pull request or something :-) ).
>> I guess it's better for the Debian package source repository to be a
>> separate one from the upstream crosstool-ng one ?
>
> Yes, some indepency from upstream has advantages
>
>
>> Alexis Murzeau
>
> Groeten
> Geert Stappers
>
>
> [1] https://github.com/crosstool-ng/crosstool-ng/tree/master/debian
>
next prev parent reply other threads:[~2017-07-24 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEUG-6j6hLoyqT8MhZmyM=OPEe=vzda_Dd7mRw8_M-ErzzzNCQ@mail.gmail.com>
2017-07-13 0:17 ` Alexis Murzeau
2017-07-17 15:44 ` Geert Stappers
[not found] ` <AM4P190MB0179FF1C5F01A494986EB730DAA00@AM4P190MB0179.EURP190.PROD.OUTLOOK.COM>
2017-07-18 19:57 ` Bug#721430: " Geert Stappers
2017-07-24 0:32 ` Chris Packham [this message]
2017-07-24 0:43 ` 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=6f770e81f1e94de6afb9b7daae4bf763@svr-chch-ex1.atlnz.lc \
--to=chris.packham@alliedtelesis.co.nz \
--cc=721430@bugs.debian.org \
--cc=amubtdx@outlook.fr \
--cc=crossgcc@sourceware.org \
--cc=stappers@stappers.nl \
/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).