From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] ntfs-3g-ntfsprogs does not rdepend on util-linux-mount
Date: Wed, 18 Sep 2013 17:13:26 +0800 [thread overview]
Message-ID: <52396EB6.3010304@windriver.com> (raw)
In-Reply-To: <52394067.6040205@topic.nl>
Hi Mike,
The reason why add util-linux-mount to RDEPENDS is the mount in
busybox doesn't support 'syntax of external mount helpers' very well.
Which means you could directly invoke mount rather than
mount.ntfs/mount.exfat
to mount ntfs/exfat filesystem.
Thanks,
Hongxu
On 09/18/2013 01:55 PM, Mike Looijmans wrote:
> Ping!
>
> Anything wrong with the patch? anyone reading this at all?
>
> BTW, the same problem is in the exfat recipe, so I was going to send a
> patch for that as well.
>
>
> On 09/12/2013 11:37 AM, Mike Looijmans wrote:
>> ntfs-3g-ntfsprogs has no runtime dependency on util-linux-mount, for
>> example busybox mount will also do just fine. It might be less useful
>> without any mount program, but that's not the same as depending on it.
>>
>> The dependency broke several images because util-linux-mount behaves
>> differently than busybox mount, resulting in failure to mount ext2/3
>> volumes and network shares on user's systems.
>>
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>> ---
>> .../ntfs-3g-ntfsprogs_2013.1.13.bb | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git
>> a/meta-filesystems/recipes-filesystems/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2013.1.13.bb
>> b/meta-filesystems/recipes-filesystems/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2013.1.13.bb
>>
>> index e084187..a34a791 100644
>> ---
>> a/meta-filesystems/recipes-filesystems/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2013.1.13.bb
>> +++
>> b/meta-filesystems/recipes-filesystems/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2013.1.13.bb
>> @@ -5,6 +5,7 @@ PROVIDES = "ntfsprogs ntfs-3g"
>> LICENSE = "GPLv2 & LGPLv2"
>> LIC_FILES_CHKSUM =
>> "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \
>> file://COPYING.LIB;md5=f30a9716ef3762e3467a2f62bf790f0a"
>> +PR = "r1"
>>
>> SRC_URI = "http://tuxera.com/opensource/ntfs-3g_ntfsprogs-${PV}.tgz"
>> S = "${WORKDIR}/ntfs-3g_ntfsprogs-${PV}"
>> @@ -23,7 +24,7 @@ EXTRA_OEMAKE = "LDCONFIG=echo"
>> PACKAGES =+ "ntfs-3g ntfsprogs libntfs-3g"
>>
>> FILES_ntfs-3g = "${base_sbindir}/*.ntfs-3g ${bindir}/ntfs-3g*
>> ${base_sbindir}/mount.ntfs"
>> -RDEPENDS_ntfs-3g += "fuse util-linux-mount"
>> +RDEPENDS_ntfs-3g += "fuse"
>>
>> FILES_ntfsprogs = "${base_sbindir}/* ${bindir}/* ${sbindir}/*"
>> FILES_libntfs-3g = "${libdir}/*${SOLIBS}"
>>
>
>
>
> Met vriendelijke groet / kind regards,
>
> Mike Looijmans
>
> TOPIC Embedded Systems
> Eindhovenseweg 32-C, NL-5683 KH Best
> Postbus 440, NL-5680 AK Best
> Telefoon: (+31) – (0)499 - 33.69.79
> Telefax: (+31) - (0)499 - 33.69.70
> E-mail: mike.looijmans@topic.nl
> Website: www.topic.nl
>
> Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn
> uitsluitend bestemd voor de geadresseerde, zoals die blijkt uit het
> e-mail bericht en/of de bijlagen. Er kunnen gegevens met betrekking
> tot een derde instaan. Indien u als niet-geadresseerde dit bericht en
> de bijlagen ontvangt, terwijl u niet bevoegd of gemachtigd bent om dit
> bericht namens de geadresseerde te ontvangen, wordt u verzocht de
> afzender hierover direct te informeren en het e-mail bericht met de
> bijlagen te vernietigen. Ieder gebruik van de inhoud van het e-mail
> bericht, waaronder de daarbij behorende bijlagen, door een ander dan
> de geadresseerde is onrechtmatig jegens ons dan wel de eventueel in
> het e-mail bericht of de bijlagen voorkomende andere personen. TOPIC
> Embedded Systems is niet aansprakelijk voor enigerlei schade
> voortvloeiend uit het gebruik en/of acceptatie van dit e-mail bericht
> of de daarbij behorende bijlagen.
>
> The contents of this message, as well as any enclosures, are addressed
> personally to, and thus solely intended for the addressee. They may
> contain information regarding a third party. A recipient who is
> neither the addressee, nor empowered to receive this message on behalf
> of the addressee, is kindly requested to immediately inform the sender
> of receipt, and to destroy the message and the enclosures. Any use of
> the contents of this message and/or the enclosures by any other person
> than the addressee or person who is empowered to receive this message,
> is illegal towards the sender and/or the aforementioned third party.
> TOPIC Embedded Systems is not liable for any damage as a result of
> the use and/or acceptance of this message and as well as any enclosures.
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2013-09-18 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 9:37 [meta-oe][PATCH] ntfs-3g-ntfsprogs does not rdepend on util-linux-mount Mike Looijmans
2013-09-18 5:55 ` Mike Looijmans
2013-09-18 9:08 ` Martin Jansa
2013-09-18 9:13 ` Hongxu Jia [this message]
2013-09-19 5:29 ` Mike Looijmans
2013-09-20 8:21 ` Mike Looijmans
2013-09-22 1:28 ` Hongxu Jia
2013-09-25 6:01 ` Mike Looijmans
2013-09-25 6:09 ` Hongxu Jia
2013-09-25 7:48 ` Mike Looijmans
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=52396EB6.3010304@windriver.com \
--to=hongxu.jia@windriver.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.