Re: Bug#721430: crosstool-ng packaging for Debian

[Chris Packham <Chris.Packham@alliedtelesis.co.nz>]

On 24/07/17 12:33, Chris Packham wrote:
> 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
>>

Sorry hit send too soon :(.

Separating them is probably a good idea short term at least. I'd like to 
get the current released version 1.23 packaged. This may require patches 
to fix lintian issues (some of which have already been applied to master).

Longer term we can decide to either maintain the packaging completely 
separately (and remove the /debian directory from crosstool-ng.git) or 
bribe Alexy to make it part of the upstream release process.