Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/asterisk
Date: Thu, 29 Nov 2007 15:39:32 +0100	[thread overview]
Message-ID: <01d701c83296$1cfb65e0$dcc4af0a@atmel.com> (raw)
In-Reply-To: d6cda7730711290551m497fb4fah54dbb7e6c67d5218@mail.gmail.com

> Hi all, Ulf,
> 
>    Doesn't changing the selects to depends on packages (such as
> asterix, ipsec, etc) affect usability quite negatively?

I am trying to get rid of the problem, that packages
"disappear" when the "depends on" are invalid.

There are also a lot of broken packages, and you 
decide that you do not want a certain package, 
since it is broken, then it takes a long time to find out what is causing 
package to be built 

This approach gives you better finetuning capabilities.

Note that once you have done your configuration, you can:

$ make saveconfig
and your project file will be saved.

If you make the "local" directory a symbolic link
to a project directory, then you can download
a new trunk, and do

make BOARD=<yourboard> getconfig

and you have all your settings back.



>    If I want to have asterisk, I go for asterisk, just to find out I
> have to enable packages in other places. If they are not optional,
> what is the point in making the user manually go thru menus looking
> for packages to select? It's not like I will give up on asterisk
> because you are making it harder to enable, right?
> 
>    So, why the changes?
> 


Best Regards
Ulf Samuelsson

  reply	other threads:[~2007-11-29 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 13:01 [Buildroot] svn commit: trunk/buildroot/package/asterisk ulf at uclibc.org
2007-11-29 13:51 ` Thiago A. Corrêa
2007-11-29 14:39   ` Ulf Samuelsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-14 15:25 aldot at uclibc.org

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='01d701c83296$1cfb65e0$dcc4af0a@atmel.com' \
    --to=ulf@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox