From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/2] strognswan: version bump 5.2.2 -> 5.3.2
Date: Wed, 1 Jul 2015 11:04:29 +0200 [thread overview]
Message-ID: <20150701090429.GK30833@pengutronix.de> (raw)
In-Reply-To: <1435672005.1861.23.camel@googlemail.com>
On Tue, Jun 30, 2015 at 03:46:45PM +0200, Christoph Fritz wrote:
> Hi Bruno,
>
> I suppose you should also add:
>
> + --disable-ruby-gems-install \
> + --disable-python-eggs-install \
Indeed. And there is a new option "--enable-files" as well.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-07-01 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 14:05 Bruno Thomsen
2015-06-29 14:05 ` [ptxdist] [PATCH 2/2] strongswan: removed md5 hash and des encryption support Bruno Thomsen
2015-06-29 17:06 ` [ptxdist] [PATCH 1/2] strognswan: version bump 5.2.2 -> 5.3.2 Jon Ringle
2015-06-30 6:27 ` Bruno Thomsen
2015-06-30 13:46 ` Christoph Fritz
2015-07-01 9:04 ` Michael Olbrich [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=20150701090429.GK30833@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox