<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font face="Ubuntu">Hi Martin, all,</font></p>
<p><font face="Ubuntu">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</font></p>
<p><font face="Ubuntu">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.</font></p>
<p><font face="Ubuntu">Thanks for your help.</font></p>
<p><font face="Ubuntu">Regards</font></p>
<p><font face="Ubuntu">Olivier</font><br>
</p>
<br>
<div class="moz-cite-prefix">Le 11/12/2016 à 13:29, Martin Winter a
écrit :<br>
</div>
<blockquote
cite="mid:4D6A895F-8542-4B1F-A565-524F16B080F7@opensourcerouting.org"
type="cite">Got all the required changes from Renato and have now
a branch
<br>
with all the Snapcraft parts ready for merge.
<br>
This includes code to modify the main Quagga and (in the snapcraft
<br>
subdir) all the needed files to build a snap.
<br>
<br>
Doc / Package files will need one more round to adjust mainly for
the
<br>
name (once we settle on something)
<br>
<br>
Branch is snapcraft_v2
<br>
<br>
Main changes:
<br>
<br>
- Snap packages are only allowed to write into their own mounted
container and the
<br>
filenames are not known until the package is installed. There
are now new —vty_socket
<br>
cli options to specify the location for the vty socket instead
of using the compile-time
<br>
path. (Plus —ctl_socket for the extra LDP socket and —config_dir
for vtysh)
<br>
<br>
- Snap packages can’t even read files outside their directories.
Getting the homedir
<br>
from the password file isn’t possible. Using now HOME env
variable and only fall back
<br>
to passed file if it doesn’t exits
<br>
<br>
- Snap packages can’t SETUID or SETGID. They always run under
root. There is now a check
<br>
for UID and GID and the change only happens if it’s not already
running under the
<br>
requested User/Group
<br>
<br>
- Martin
<br>
<br>
_______________________________________________
<br>
cmaster-next mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:cmaster-next@lists.nox.tf">cmaster-next@lists.nox.tf</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.nox.tf/listinfo/cmaster-next">https://lists.nox.tf/listinfo/cmaster-next</a>
<br>
</blockquote>
<br>
<PRE>_________________________________________________________________________________________________________________________
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.
</PRE></body>
</html>