From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] udftools: new package
Date: Wed, 31 Jan 2018 15:57:28 +0100 [thread overview]
Message-ID: <20180131145728.GD13531@gmail.com> (raw)
In-Reply-To: <20180122213138.11855-1-skenton@ou.edu>
Hi Steve,
On Mon, Jan 22, 2018 at 03:31:38PM -0600, Steve Kenton wrote:
> Signed-off-by: Steve Kenton <skenton@ou.edu>
> I computed the hash below for the license file but I did not see any others under the package directory
> so I think I must be misunderstanding where it should go from my reading of the on-line manual
?
> # Locally computed
> sha256 dcc100d4161cc0b7177545ab6e47216f84857cda3843847c792a25289852dcaa COPYING
> I ran ./utils/check-package package/udftools/* and fixed up all the white space errors
> But I'm not sure what to do with ./utils/test-pkg, do I need to build all 47 tools chains?
> I tried ./utils/test-pkg -p udftools -c udftools.snippet (contents below) but just got errors
> BR2_PACKAGE_UDFTOOLS=y
> diff --git a/package/udftools/udftools.hash b/package/udftools/udftools.hash
> new file mode 100644
> index 0000000..b297edf
> --- /dev/null
> +++ b/package/udftools/udftools.hash
> @@ -0,0 +1,2 @@
> +# Locally computed
Sorry, I don't understand your comments. The computed hash should go
here
> +sha256 67fe428d452901215cfad8049d250540c97114b1a20dd63277b91c2c4fae8292 udftools-2.0.tar.gz
sha256 dcc100d4161cc0b7177545ab6e47216f84857cda3843847c792a25289852dcaa COPYING
> diff --git a/package/udftools/udftools.mk b/package/udftools/udftools.mk
> new file mode 100644
> index 0000000..708fef9
> --- /dev/null
> +++ b/package/udftools/udftools.mk
> @@ -0,0 +1,12 @@
> +################################################################################
> +#
> +# udftools
> +#
> +################################################################################
> +
> +UDFTOOLS_VERSION = 2.0
> +UDFTOOLS_SITE = https://github.com/pali/udftools/releases/download/$(UDFTOOLS_VERSION)
> +UDFTOOLS_LICENSE = GPL-2.0+
The license is "GPL-2.0".
> +UDFTOOLS_LICENSE_FILES = COPYING
> +
> +$(eval $(autotools-package))
> --
> 2.9.0.137.gcf4c2cf
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Best regards
Marcus Folkesson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180131/2c2695f6/attachment.asc>
next prev parent reply other threads:[~2018-01-31 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 21:31 [Buildroot] [PATCH 1/1] udftools: new package Steve Kenton
2018-01-31 14:57 ` Marcus Folkesson [this message]
2018-02-06 16:08 ` Thomas Petazzoni
2018-02-08 13:22 ` Marcus Folkesson
2018-02-08 14:20 ` Thomas Petazzoni
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=20180131145728.GD13531@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=buildroot@busybox.net \
/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