All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [oe-commits] Koen Kooi : initscripts: only run ldconfig on boot when ld.so. conf is present
Date: Sun, 02 Nov 2008 08:45:30 +0100	[thread overview]
Message-ID: <gejlqq$ivd$1@ger.gmane.org> (raw)
In-Reply-To: <1225567242.4235.471.camel@lenovo.internal.reciva.com>

On 01-11-2008 20:20, Phil Blundell wrote:

> Just as an aside, there isn't really any need to have complicated
> runtime logic to handle all possible combinations of DISTRO policy.  Any
> single DISTRO would clearly have only one policy (for example, either it
> uses a package manager or it doesn't) and hence it can make these
> determinations at build time.

That's awfully shortsighted and not the direction OE has been going in 
for the past years. A small example:

* kernel
* initramfs/initrd
* rootfs

Only the rootfs has a packagemanager, but the initramfs/initrd doesn't. 
This shows that a single distro can build image both with and without 
packagemanagement.
Saying "distros should only do <foo>" is for the distros to decide.

regards,

Koen




  reply	other threads:[~2008-11-02  7:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081031110045.7EF89189333@amethyst.openembedded.net>
2008-10-31 12:37 ` [oe-commits] Koen Kooi : initscripts: only run ldconfig on boot when ld.so. conf is present Carsten Haitzler
2008-10-31 15:55   ` Koen Kooi
2008-10-31 21:53     ` Carsten Haitzler
2008-11-01  8:22       ` Koen Kooi
2008-11-01 11:38         ` Stanislav Brabec
2008-11-01 19:20           ` Phil Blundell
2008-11-02  7:45             ` Koen Kooi [this message]
2008-11-01 23:08           ` Carsten Haitzler
2008-11-02  4:51             ` Denys Dmytriyenko
2008-11-02  6:37               ` Carsten Haitzler
2008-11-02 10:52             ` Stanislav Brabec
2008-11-02 11:25               ` Running one-off target binaries, was: " 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='gejlqq$ivd$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.