< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] compiling nICEr



On 21/09/15 21:49, Daniel Pocock wrote:
> 
> 
> On 20/09/15 16:05, docfaraday@xxxxxxxxx wrote:
>>
>>
>>
>>
>>> On Sep 20, 2015, at 3:38 AM, Daniel Pocock <daniel@xxxxxxxxxx> wrote:
>>>
>>>
>>>
>>>> On 20/09/15 03:08, Byron Campen wrote:
>>>>> On 9/19/15 1:49 PM, Daniel Pocock wrote:
>>>>>
>>>>>> On 19/09/15 14:58, docfaraday@xxxxxxxxx wrote:
>>>>>>    You would definitely need to pull nrappkit from Mozilla's
>>>>>> codebase. We've had "fixing nICEr's public build" on the todo list
>>>>>> for a while, but you're the first that has expressed an interest that
>>>>>> I'm aware of. If you run into more breakage after pulling the current
>>>>>> nrappkit (and you probably will, since the build system hasn't been
>>>>>> fully updated yet) give me a shout and I can help.
>>>>> Hi Byron,
>>>>>
>>>>> It is hard for me to support this code as part of the reSIProcate
>>>>> release and packaging processes too.  In fact, it is not even mentioned
>>>>> in the Makefile.am right now.
>>>>>
>>>>> Should we consider splitting it into a separate repository?  git
>>>>> filter-branch will let you fully extract the history of the nICEr
>>>>> directory into a separate repository.  You could then potentially use
>>>>> that new repository as a Git submodule for building Mozilla things too.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Daniel
>>>>> _______________________________________________
>>>>> resiprocate-devel mailing list
>>>>> resiprocate-devel@xxxxxxxxxxxxxxx
>>>>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>>>>   This is something we've wanted to do for a while, but just could not
>>>> justify the effort compared to other stuff on our plate.
>>>
>>> If you like, I can try running git filter-branch and putting the nICEr
>>> tree into another repository under https://github.com/resiprocate/nICEr
>>> for you.
>>>
>>> If you only want the stuff from the master branch and if you don't care
>>> that the commit hashes will change then it is quite straightforward.
>>>
>>> If you have other clones or forks of this work though, you may have to
>>> manually rebase them against the new repository.
>>>
>>> Regards,
>>>
>>> Daniel
>>> _______________________________________________
>>> resiprocate-devel mailing list
>>> resiprocate-devel@xxxxxxxxxxxxxxx
>>> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>>
>>     I don't have any problem with commit hashes changing.
>>
> 
> Ok, done.  You can find the nICEr/* tree from master here:
> 
>   https://github.com/resiprocate/nICEr
> 
> If there is stuff on branches too please let me know and I'll try to
> find a way to get them over.
> 
> If it is OK there then please tell me and I'll make a commit deleting
> the nICEr directory in the resiprocate repository.  The history will
> still be in the main repository of course, but you also have a copy of
> the history in the standalone repository.
> 


As discussed, the nICEr tree has now been removed from the main
resiprocate repository and it is in the new repository:

https://github.com/resiprocate/nICEr