From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] powerpc-utils: remove --without-librtas
Date: Mon, 11 May 2015 07:34:45 +0300 [thread overview]
Message-ID: <20150511043445.GO2558@tarshish> (raw)
In-Reply-To: <554FFB2F.2010102@au1.ibm.com>
Hi Sam,
On Mon, May 11, 2015 at 10:43:27AM +1000, Sam Bobroff wrote:
> On 08/05/15 14:57, Baruch Siach wrote:
> > On Fri, May 08, 2015 at 02:27:49PM +1000, Sam Bobroff wrote:
> >> -POWERPC_UTILS_DEPENDENCIES = zlib
> >> +POWERPC_UTILS_DEPENDENCIES = zlib librtas
> >
> > Why not make librtas an optional dependency? Something like:
> >
> > ifeq ($(BR2_PACKAGE_LIBRTAS),y)
> > POWERPC_UTILS_DEPENDENCIES += librtas
> > POWERPC_UTILS_CONF_OPTS = --with-librtas
> > else
> > POWERPC_UTILS_CONF_OPTS = --without-librtas
> > endif
>
> I thought about making it optional, but there seemed to be two reasons
> to always include it:
>
> * librtas is a small library and it provides a lot of functionality to
> powerpc-utils. Why leave it out?
>
> * Distros (AFAIK) always include librtas when providing powerpc-utils,
> so it would surprise users to provide a powerpc-utils without it by
> default. So if I did make it optional, I think it should be using some
> method that caused librtas to be included by default or at least
> provided some indication in the menu that they may want to go and enable
> librtas. Then I thought this was a bit complicated for a use case that I
> couldn't find a reason for.
These are valid reasons. What is the target installed size of librtas compared
to powerpc-utils?
> That said, if you have a reason to make it optional I'll be happy to
> make it so. Maybe using a sub-option to add the dependency, and that
> could default to yes?
>
> e.g.
>
> [*] powerpc-utils
> [*] RTAS functionality
Sounds reasonable to me. Let's see what others think.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-05-11 4:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 4:27 [Buildroot] [PATCH 0/2] Improve powerpc-utils with librtas Sam Bobroff
2015-05-08 4:27 ` [Buildroot] [PATCH 1/2] librtas: new package Sam Bobroff
2015-05-08 4:52 ` Baruch Siach
2015-05-08 5:37 ` Sam Bobroff
2015-05-08 7:42 ` Peter Korsgaard
2015-05-10 23:58 ` Sam Bobroff
2015-05-11 9:31 ` Thomas Petazzoni
2015-05-08 4:27 ` [Buildroot] [PATCH 2/2] powerpc-utils: remove --without-librtas Sam Bobroff
2015-05-08 4:57 ` Baruch Siach
2015-05-11 0:43 ` Sam Bobroff
2015-05-11 4:34 ` Baruch Siach [this message]
2015-05-11 5:53 ` Sam Bobroff
2015-05-11 6:00 ` Baruch Siach
2015-05-11 7:56 ` Peter Korsgaard
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=20150511043445.GO2558@tarshish \
--to=baruch@tkos.co.il \
--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.