All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 02/11] ntfs-3g-ntfsprogs: add 2011.4.12 recipes
Date: Sun, 08 May 2011 10:33:42 +0200	[thread overview]
Message-ID: <iq5kh6$gie$2@dough.gmane.org> (raw)
In-Reply-To: <1304822586-14872-2-git-send-email-otavio@ossystems.com.br>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08-05-11 04:42, Otavio Salvador wrote:
> This recipe is a merge of ntfs-3g and ntfsprogs thus the provides
> entries.
> 
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>  .../ntfs-3g-ntfsprogs_2011.4.12.bb                 |   26 ++++++++++++++++++++
>  1 files changed, 26 insertions(+), 0 deletions(-)
>  create mode 100644 meta-oe/recipes-support/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2011.4.12.bb
> 
> diff --git a/meta-oe/recipes-support/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2011.4.12.bb b/meta-oe/recipes-support/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2011.4.12.bb
> new file mode 100644
> index 0000000..561f52a
> --- /dev/null
> +++ b/meta-oe/recipes-support/ntfs-3g-ntfsprogs/ntfs-3g-ntfsprogs_2011.4.12.bb
> @@ -0,0 +1,26 @@
> +DESCRIPTION = "The NTFS-3G driver is an open source, freely available NTFS driver for Linux with read and write support."
> +HOMEPAGE = "http://www.ntfs-3g.org/"
> +DEPENDS = "fuse libgcrypt"
> +PROVIDES = "ntfsprogs ntfs-3g"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 \

COPYING.LIB implies LGPL components, is the LICENSE field correct?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNxlVmMkyGM64RGpERAqDFAJ0QhXNSCswuFqlNsz3stWeNCVkCUACgkahC
MmFKCMti+j7qg4wj8ENjGDQ=
=qPAD
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2011-05-08  8:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08  2:42 [meta-oe][PATCH 01/11] fuse: add 2.8.5 Otavio Salvador
2011-05-08  2:42 ` [meta-oe][PATCH 02/11] ntfs-3g-ntfsprogs: add 2011.4.12 recipes Otavio Salvador
2011-05-08  6:34   ` Paul Menzel
2011-05-08  8:34     ` Koen Kooi
2011-05-08  8:47       ` Paul Menzel
2011-05-08 16:13     ` Otavio Salvador
2011-05-08  8:33   ` Koen Kooi [this message]
2011-05-08  8:56   ` Phil Blundell
2011-05-08  2:42 ` [meta-oe][PATCH 03/11] setxkbmap: add 1.2.0 version Otavio Salvador
2011-05-08  6:36   ` Paul Menzel
2011-05-08  2:42 ` [meta-oe][PATCH 04/11] freerdp: add recipe based on GIT from 2009-03-29 Otavio Salvador
2011-05-08  2:43 ` [meta-oe][PATCH 05/11] pixman.inc: use Xorg mirror Otavio Salvador
2011-05-08  2:43 ` [meta-oe][PATCH 06/11] p910nd: add 0.95 version Otavio Salvador
2011-05-08  2:43 ` [meta-oe][PATCH 07/11] libiconv: drop hack since gettext was being inherited Otavio Salvador
2011-05-08  2:43 ` [meta-oe][PATCH 08/11] libinih: add git recipe Otavio Salvador
2011-05-08  2:43 ` [meta-oe][PATCH 09/11] qt4: drop 4.6 versions Otavio Salvador
2011-05-08  2:43 ` [meta-oe][PATCH 10/11] postgresql: update to 8.4.7 since 8.4.4 was unfetchable Otavio Salvador
2011-05-08  2:43 ` [meta-oe][PATCH 11/11] qt4: fix 4.7.2 checksum Otavio Salvador
2011-05-08  4:50   ` Martin Jansa
2011-05-08  5:07     ` Otavio Salvador
2011-05-08  6:30 ` [meta-oe][PATCH 01/11] fuse: add 2.8.5 Paul Menzel
2011-05-08 16:32   ` Otavio Salvador

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='iq5kh6$gie$2@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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.