From: Ned Ludd <solar@gentoo.org>
To: Natanael Copa <mlists@tanael.org>
Cc: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] emerge/tbz2pkg for busybox
Date: Tue, 12 Apr 2005 12:40:11 -0400 [thread overview]
Message-ID: <1113324011.25607.41.camel@localhost> (raw)
In-Reply-To: <1113313173.15836.61.camel@nc>
On Tue, 2005-04-12 at 15:39 +0200, Natanael Copa wrote:
> On Sat, 2005-04-09 at 12:17 -0400, Ned Ludd wrote:
> > Hi guys.. checking in. Are we feeling these two applets (tgz2pkg/emerge)
> > are getting close to being ready for use yet? Or have we stalled?
> > Waiting on me for anything?
>
> I'm sorry. I almost forgot this.
>
> I have sent the (almost) complete tbz2pkg to Benjamin. There were some
> cleanup needed so they shared the data. Last thing I heard from Benjamin
> was that I'm more or less done with my part.
Ok thanks for the update. Hopefully we will hear from him soon, not
sure if the not having a public CVS for you both to work within has
been a problem or if he's just been real busy.
> There is one thing that concerns me though...
>
> Preistall/postinstall scripts. I think we will depend on having scripts
> attatched to the packages that could be executed (for creating users,
> handling updates etc...)
>
> Any idea on how this could be handled?
sadly no I do not. have any creative ideas on how to handle this part
other than reviewing, trial and error while testing the ebuilds 1 at a
time. Some for example will have bash only commands and expressions in
the pkg_postinst(), pkg_preinst() that's going to fsck our worlds up.
In such cases I see no way around that other than to provide our own
init script and sometimes conf.d/init.d replacements.
iggy has been working on the backend for the baselayout-lite as _pre2
and should have a bit of the framework we will want for our scripts in
place. If you all done with the tbz2 tool perhaps you could check that
out and help there towards pre3 with how the other new tools will play
in if you are still wanting to pitch in and help. :)
Side for those that think smaller is better and I don't know where else
to say this. But if your not using java and will never be on your
embedded devices you can save about an extra 48 bytes per every
ELF DY_DYN and ET_EXEC file by stripping the .jcr section.
So together with the .comment and .jcr you can save about ~300 bytes.
# grep STRIP /etc/make.conf
PORTAGE_STRIP_FLAGS="--strip-unneeded -R .note -R .comment -R .jcr"
--
Ned Ludd <solar@gentoo.org>
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-12 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1110902754.19237.12.camel@nc>
2005-04-09 16:17 ` [gentoo-embedded] emerge/tbz2pkg for busybox Ned Ludd
2005-04-12 13:39 ` Natanael Copa
2005-04-12 16:40 ` Ned Ludd [this message]
2005-04-19 5:10 ` Peter S. Mazinger
2005-04-19 13:56 ` Ned Ludd
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=1113324011.25607.41.camel@localhost \
--to=solar@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=mlists@tanael.org \
/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