[cmaster-next] Snapcraft_v2 branch ready for merge into stable/2.0

[Christian Franke]

Hello,

it's on https://github.com/opensourcerouting/cumulus-private_quagga/

-Christian

On 12/12/2016 03:01 PM, olivier.dugeon at orange.com wrote:
> Hi Martin, all,
> 
> I certainly miss the information, sorry for that (or the mail was delete
> by our anti-spam filter), but I can't figure where are located this
> branch as well as the stable 2.0
> 
> Is it on the github cumulus private repo cmaster-next or elsewhere ? I
> look to the cmaster-next git repo, but didn't found any reference to
> stable 2.0 or snapcraft_v2.
> 
> Thanks for your help.
> 
> Regards
> 
> Olivier
> 
> 
> Le 11/12/2016 à 13:29, Martin Winter a écrit :
>> Got all the required changes from Renato and have now a branch
>> with all the Snapcraft parts ready for merge.
>> This includes code to modify the main Quagga and (in the snapcraft
>> subdir) all the needed files to build a snap.
>>
>> Doc / Package files will need one more round to adjust mainly for the
>> name (once we settle on something)
>>
>> Branch is  snapcraft_v2
>>
>> Main changes:
>>
>> - Snap packages are only allowed to write into their own mounted
>> container and the
>>   filenames are not known until the package is installed. There are
>> now new —vty_socket
>>   cli options to specify the location for the vty socket instead of
>> using the compile-time
>>   path. (Plus —ctl_socket for the extra LDP socket and —config_dir for
>> vtysh)
>>
>> - Snap packages can’t even read files outside their directories.
>> Getting the homedir
>>   from the password file isn’t possible. Using now HOME env variable
>> and only fall back
>>   to passed file if it doesn’t exits
>>
>> - Snap packages can’t SETUID or SETGID. They always run under root.
>> There is now a check
>>   for UID and GID and the change only happens if it’s not already
>> running under the
>>   requested User/Group
>>
>> - Martin
>>
>> _______________________________________________
>> cmaster-next mailing list
>> cmaster-next at lists.nox.tf
>> https://lists.nox.tf/listinfo/cmaster-next
> 
> _________________________________________________________________________________________________________________________
> 
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> 
> 
> 
> _______________________________________________
> cmaster-next mailing list
> cmaster-next at lists.nox.tf
> https://lists.nox.tf/listinfo/cmaster-next
>