Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Jain <rahul.jain@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/3] uhttpd: new package
Date: Mon, 17 Oct 2016 15:55:26 +0530	[thread overview]
Message-ID: <5804A716.4000408@imgtec.com> (raw)
In-Reply-To: <f1551376-9c0b-1d15-4e90-4a70a9f7b66d@imgtec.com>

Hi Vicente,

Thanks for your comments.

On Friday 14 October 2016 08:20 PM, Vicente Olivert Riera wrote:
>> diff --git a/package/uhttpd/uhttpd.mk b/package/uhttpd/uhttpd.mk
>> new file mode 100644
>> index 0000000..b4ef291
>> --- /dev/null
>> +++ b/package/uhttpd/uhttpd.mk
>> @@ -0,0 +1,38 @@
>> +################################################################################
>>
>> +#
>> +# uhttpd
>> +#
>> +################################################################################
>>
>> +
>> +UHTTPD_VERSION = 59e0c739634f46a164d939e54416287b91ff8a9b
>> +UHTTPD_SITE = http://git.openwrt.org/project/uhttpd.git
>> +UHTTPD_SITE_METHOD = git
>> +UHTTPD_LICENSE = ISC
>
> Same thing here, UHTTPD_LICENSE_FILES is missing. You are saying that
> the license is ISC, but, how can you check it? You need some file to
> look at in order to check it.
>
The package does not provide any license file, but all the source files 
have the ISC license header. I will add one of the source file as the
license file.

Thanks,
Rahul Jain

  reply	other threads:[~2016-10-17 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 10:45 [Buildroot] [PATCH v3 1/3] ustream-ssl: new package Rahul Jain
2016-10-10 10:45 ` [Buildroot] [PATCH v3 2/3] uhttpd: " Rahul Jain
2016-10-14 14:50   ` Vicente Olivert Riera
2016-10-17 10:25     ` Rahul Jain [this message]
2016-10-10 10:45 ` [Buildroot] [PATCH v3 3/3] DEVELOPERS: add entry for uhttpd and ustream-ssl Rahul Jain

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=5804A716.4000408@imgtec.com \
    --to=rahul.jain@imgtec.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