All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] samba4: bump to version 4.1.10
Date: Thu, 31 Jul 2014 00:31:18 +0200	[thread overview]
Message-ID: <20140731003118.322103fe@free-electrons.com> (raw)
In-Reply-To: <53D96C6E.5060203@zacarias.com.ar>

Dear Gustavo Zacarias,

On Wed, 30 Jul 2014 19:06:38 -0300, Gustavo Zacarias wrote:

> The binaries are installed in /usr/bin & /usr/sbin, but they are python
> scripts that import from the usual /usr/lib/python2.7/site-packages/* (a
> couple in the toplevel, most in samba/).
> Alternatively we can remove the tools if .pyc files aren't kept or hide
> samba4.
> But since that doesn't inhibit samba4 working and most people would
> probably make up their config from some template or separate web ui i
> went for the warning.
> It would probably be problematic for advanced uses like clustering or
> ADS support which aren't part of the feature set of the package at the
> moment (and stumbled upon it when testing what that would entail).

Then wouldn't it be simpler/saner to simply remove those tools and
Python modules from the target completely?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-07-30 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 18:15 [Buildroot] [PATCH] samba4: bump to version 4.1.10 Gustavo Zacarias
2014-07-29 18:22 ` Thomas Petazzoni
2014-07-29 18:54   ` Gustavo Zacarias
2014-07-30 21:58     ` Thomas Petazzoni
2014-07-30 22:06       ` Gustavo Zacarias
2014-07-30 22:31         ` Thomas Petazzoni [this message]
2014-07-31  1:28           ` Gustavo Zacarias

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=20140731003118.322103fe@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.