mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Alexander Aring <alex.aring@gmail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 3/3] iputils: add new package iputils
Date: Sat, 25 Jan 2014 15:00:28 +0100	[thread overview]
Message-ID: <20140125140028.GN12605@pengutronix.de> (raw)
In-Reply-To: <20140125135411.GB17307@omega>

On Sat, Jan 25, 2014 at 02:54:12PM +0100, Alexander Aring wrote:
> On Sat, Jan 25, 2014 at 02:49:51PM +0100, Robert Schwebel wrote:
> > The || ALLYES comment applies here as well.
> 
> ok. What means ALLYES in this case? I suppose something with
> allyesconfig?

We have an "ALLYES" BSP in our autobuilder. It has PTXCONF_ALLYES set,
which makes it possible to build everything, even the packages which
have equivalents in busybox.

rsc
-- 
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

  reply	other threads:[~2014-01-25 14:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25 13:18 [ptxdist] [PATCH 1/3] inetutils: add misiing depends on !BUSYBOX_TFTPD Alexander Aring
2014-01-25 13:18 ` [ptxdist] [PATCH 2/3] gnutls: add support for openssl compatibility Alexander Aring
2014-01-27  9:48   ` Michael Olbrich
2014-01-27 10:06     ` Alexander Aring
2014-01-25 13:18 ` [ptxdist] [PATCH 3/3] iputils: add new package iputils Alexander Aring
2014-01-25 13:49   ` Robert Schwebel
2014-01-25 13:54     ` Alexander Aring
2014-01-25 14:00       ` Robert Schwebel [this message]
2014-01-25 14:01         ` Alexander Aring
2014-01-25 13:48 ` [ptxdist] [PATCH 1/3] inetutils: add misiing depends on !BUSYBOX_TFTPD Robert Schwebel
2014-01-25 13:50   ` Alexander Aring

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=20140125140028.GN12605@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=alex.aring@gmail.com \
    --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