From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: upstart vs. task-proper-tools
Date: Wed, 24 Aug 2011 16:34:06 +0200 [thread overview]
Message-ID: <4E550BDE.6010401@dresearch-fe.de> (raw)
In-Reply-To: <4E54F03E.3040806@juszkiewicz.com.pl>
On 24.08.2011 14:36, Marcin Juszkiewicz wrote:
> W dniu 24.08.2011 14:31, Steffen Sledz pisze:
>> BTW:
>> What is the exact meaning/purpose/use of task-proper-tools?
>
> Replace busybox components by full versions. Was made years ago and then
> updated by several people. While working for BugLabs company I used it
> to create rootfs without busybox.
>
>> The list contains a lot of tools with existing alternatives (e.g. syslog-ng vs. rsyslog or pump vs. dhcpcd).
>
> Then propose change which will allow to install one of them only at time?
Sorry, but my knowledge is not sufficient to do this. I've no idea how to reference u-a related tools here.
Who can help?
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-08-24 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 11:03 upstart vs. task-proper-tools Steffen Sledz
2011-08-24 12:31 ` Steffen Sledz
2011-08-24 12:36 ` Marcin Juszkiewicz
2011-08-24 14:34 ` Steffen Sledz [this message]
2011-08-24 14:45 ` Martin Jansa
2011-08-24 14:57 ` Steffen Sledz
2011-08-24 15:14 ` Martin Jansa
2011-08-24 17:06 ` Steffen Sledz
2011-08-24 14:26 ` Cliff Brake
2011-08-24 14:31 ` Steffen Sledz
2011-08-24 15:19 ` Koen Kooi
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=4E550BDE.6010401@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.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