From: Philippe Ney <philippe.ney@pardes.ws>
To: buildroot@busybox.net
Subject: [Buildroot] patch: target/cpio
Date: Wed, 22 Nov 2006 08:53:53 +0100 [thread overview]
Message-ID: <20061122085353.a872873b.philippe.ney@pardes.ws> (raw)
In-Reply-To: <20061121095514.GK3065@priv.blacknet.de>
> > > this patch adds a simple cpio target, to be used with an initramfs
>
> > In my application, as I also use cpio on the target, then I added a cpio
> > package that provide target and host cpio.
> > I use it to update the initramfs and have a simple dynamic RIM system w/o
> > use of cramfs/unionfs.
> >
> > If this could be useful, I will make a patch.
>
> Shure, please provide a patch.
>
> BTW: I wonder why there are hundrets^Wdozens of buildroot forkes, all
> with more up to date/additional packages and noone ever seams to
> provide patches on their own.
> Do they think that buildroot is to unmodular that additional stuff
> would make it to bloated for the rest? Or is the addition just a
> hack, they always wanted to clean up, just never found the time to
> do so? Or do they simply not care?
> - Just wondering.
I use a old version of buildroot that I modified/simplified for my own
needs. I don't know at this time if my additional stuff works with the
current one.
It's mainly hack that often don't build automatically but need manual
action. Which is sufficient for my own needs but I think it's not for
beeing added in the buildroot trunk. It is also only tested on an i386
target which seems not sufficient for me to be added in buildroot, isn't
it ?
For example I worked on porting perl but I didn't succeeded on having it
working with dynamic loading (for modules). I have a working static perl
(with static modules built-in) but it need to have a special config file
that contains the static built-in modules whereas this should be more
flexible. The Crypt:SSLay module need the path to OpenSSL and I give it
manually, et coetera.
Philippe
next prev parent reply other threads:[~2006-11-22 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 15:44 [Buildroot] patch: target/cpio Goetz Bock
2006-11-20 17:01 ` Philippe Ney
2006-11-21 9:55 ` Goetz Bock
2006-11-22 7:53 ` Philippe Ney [this message]
2006-11-22 18:56 ` Philippe Ney
2006-11-22 19:17 ` Bernhard Fischer
2006-11-22 21:34 ` Philippe Ney
2006-11-23 8:19 ` Goetz Bock
2006-11-22 19:16 ` Bernhard Fischer
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=20061122085353.a872873b.philippe.ney@pardes.ws \
--to=philippe.ney@pardes.ws \
--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