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 v3] classpath: bump to version 0.99
Date: Mon, 13 Feb 2017 17:46:08 +0100	[thread overview]
Message-ID: <20170213174608.1af2c81b@free-electrons.com> (raw)
In-Reply-To: <87wpcukqe1.fsf@dell.be.48ers.dk>

Hello,

On Mon, 13 Feb 2017 17:27:18 +0100, Peter Korsgaard wrote:

>  > Agreed. But that creates a kind of weird circular dependency, no?  
> 
>  > Or perhaps we should just get rid of the prompt for classpath
>  > completely?  
> 
> Either that or dropping the 'depends on jamvm' from classpath. It indeed
> isn't very useful without a jvm, but it still builds Ok and I guess a
> lot of other package combinations also don't make a lot of sense.

I think it's a better option than making the classpath package
invisible. Indeed, if we make it invisible, users might wonder if we
have "support" for it.

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

  reply	other threads:[~2017-02-13 16:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12  1:47 [Buildroot] [PATCH 1/1] classpath: bump to version 0.99 Marcus Hoffmann
2017-02-12  1:54 ` [Buildroot] [PATCH v2] " Marcus Hoffmann
2017-02-12  2:04   ` [Buildroot] [PATCH v3] " Marcus Hoffmann
2017-02-12 14:14     ` Thomas Petazzoni
2017-02-12 15:36       ` Marcus Hoffmann
2017-02-13 13:29         ` Thomas Petazzoni
2017-02-13 15:08           ` Marcus Hoffmann
2017-02-13 16:05           ` Peter Korsgaard
2017-02-13 16:09             ` Thomas Petazzoni
2017-02-13 16:27               ` Peter Korsgaard
2017-02-13 16:46                 ` Thomas Petazzoni [this message]
2017-02-12 14:41     ` Thomas Petazzoni
2017-02-12 15:00       ` Marcus Hoffmann

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=20170213174608.1af2c81b@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.