From: Mike <mike-gmanemailinglistnospam@tiedyenetworks.com>
To: buildroot@busybox.net
Subject: [Buildroot] package selections vs openwrt
Date: Tue, 04 May 2010 07:51:27 -0700 [thread overview]
Message-ID: <hrpc9h$cha$1@dough.gmane.org> (raw)
Howdy,
I was just wondering if anyone had any comment on the size of the
'feeds' available from OpenWRT vs Buildroot. It seems there's a lot more
packages that have been pulled into that system (742 for feeds alone)
even tho there's a common heritage, those have not been similarly pulled
into buildroot and it's seems a bit duplicitous? Openwrt has a full on
build of perl 5.10 for example, which appears to be a very hairy and
non-trivial job to import as a buildroot project for example (but very
desirable for me). On the other end of scale however many of those
packages also appear to be old, insecure / known buggy versions. It
would just be great for there to be some sort of import of those
packages so at least they could be updated and used within the general
buildroot system and not tailored just for the more narrow focused
openwrt effort. I guess Im just wondering why there doesn't seem to be
much overlap or cross project collaboration ?
Thanks.
Mike-
reply other threads:[~2010-05-04 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='hrpc9h$cha$1@dough.gmane.org' \
--to=mike-gmanemailinglistnospam@tiedyenetworks.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