All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Lerche <robert.lerche@msbit.com>
To: buildroot@busybox.net
Subject: [Buildroot] Private mirror repository for Python package dependencies -- howto?
Date: Tue, 3 Oct 2017 13:51:55 -0700	[thread overview]
Message-ID: <CAF7SrrFDHt1=+a0DcJUBrwk7vL_01Kd8YfyCBKFswCtLw3TEBg@mail.gmail.com> (raw)
In-Reply-To: <20170929215151.35dea574@windsurf>

Thanks for your response.

At the request of one of our developers I added Python connexion (
https://pypi.python.org/pypi/connexion) which in turn pulled in a bunch of
other components (flake8, mccabe, pyflakes, pycodestyle, pytest-runner).

Reading between the lines of your mail, I added each of those components
individually to my customized Buildroot and that takes care of the issue.

On Fri, Sep 29, 2017 at 12:51 PM, Thomas Petazzoni <
thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Fri, 29 Sep 2017 09:53:25 -0700, Robert Lerche wrote:
> > Buildroot provides a simple and effective means to specify a private
> mirror
> > for package source code components (BR2_PRIMARY_SITE).  This is essential
> > for a company basing an embedded system product on Buildroot.
> >
> > Is there an equivalent mechanism to support a private repository for
> Python
> > package dependencies?  Otherwise distutils and setuptools will fetch from
> > public sources even though the package base comes from the private
> mirror.
>
> This should never happen. If a Python package downloads its
> dependencies by itself without going through Buildroot's download
> mechanism, it's a bug.
>
> Could you give a more specific example of a problematic Python package ?
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20171003/2334f1fd/attachment.html>

      reply	other threads:[~2017-10-03 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 16:53 [Buildroot] Private mirror repository for Python package dependencies -- howto? Robert Lerche
2017-09-29 19:51 ` Thomas Petazzoni
2017-10-03 20:51   ` Robert Lerche [this message]

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='CAF7SrrFDHt1=+a0DcJUBrwk7vL_01Kd8YfyCBKFswCtLw3TEBg@mail.gmail.com' \
    --to=robert.lerche@msbit.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.