From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev PDA-like machines with card slots: Enable "vfat" feature.
Date: Wed, 19 Dec 2007 11:14:21 +0200 [thread overview]
Message-ID: <737651158.20071219111421@gmail.com> (raw)
In-Reply-To: <4768D18E.2000105@student.utwente.nl>
Hello Koen,
Wednesday, December 19, 2007, 10:08:46 AM, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Rod Whitby schreef:
>> pHilipp Zabel wrote:
>>>> So now that we have the easy method implemented, let's strive for a correct one.
>>>> I'd say vfat as other file systems should be a distro-only feature,
>>>> cardslot (or "removablestorage") a machine-only one:
>>>> "vfat" in DISTRO_FEATURES and "cardslot" in MACHINE_FEATURES --> task-base-vfat
>>>> "ext2" in DISTRO_FEATURES and ("cardslot" in MACHINE_FEATURES or "hdd"
>>>> in MACHINE_FEATURES) --> task-base-ext2 (without the hdparm
>>>> dependency)
>>>> "hdd" in MACHINE_FEATURES --> hdparm
>>>> etc.
>>
>> I agree with the principle. We also need to add 'usbhost' to the list
>> of machine features which can enable the ext2 and vfat distro features
>> (for usb flash sticks on devices with usb host ports).
>>
>> And of course we need to work out the best way (and appropriate timing)
>> for implementation. :-)
>>
>> Marcin, Koen, Richard: Do you guys have an opinion on this
>> machine/distro features independent naming and combinations of different
>> names feeding into combined features? We need agreement on the
>> principle before getting too far into implementation discussion.
> My opinion is that 'DISTRO_*' is a misnomer since it essentially decides
> what gets into an image.
But the content of the image is one of the most important aspect of
the distro! Actually, a distro in OE is nothing but a name associated
with a set of specific packages with specific versions, with the name
being patched in some packages. So, how "DISTRO_FEATURES" can be a
misnomer?
> But it works on a 'global' task-base, so it
> isn't IMAGE_* either. Maybe we should have a look at what Steve Sakoman
> cooked up for the gumstix people.
> regards,
> Koen
--
Best regards,
Paul mailto:pmiscml@gmail.com
prev parent reply other threads:[~2007-12-19 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1J4SUo-0006ZZ-Ov@linuxtogo.org>
2007-12-18 10:17 ` [oe-commits] org.oe.dev PDA-like machines with card slots: Enable "vfat" feature pHilipp Zabel
2007-12-18 11:35 ` Paul Sokolovsky
2007-12-18 14:38 ` pHilipp Zabel
2007-12-18 15:05 ` Paul Sokolovsky
2007-12-18 18:13 ` pHilipp Zabel
2007-12-18 19:22 ` Paul Sokolovsky
2007-12-18 21:07 ` Rod Whitby
2007-12-19 8:08 ` Koen Kooi
2007-12-19 9:14 ` Paul Sokolovsky [this message]
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=737651158.20071219111421@gmail.com \
--to=pmiscml@gmail.com \
--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 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.