Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/asn1c: new host package
Date: Sun, 19 Apr 2020 06:41:29 +0300	[thread overview]
Message-ID: <87imhwcfbq.fsf@tarshish> (raw)
In-Reply-To: <CAEyMn7Y=aY1zO0Wm5wVzHrdmn=CDrzJJ=aepgm5rXXJ4Hir-uw@mail.gmail.com>

Hi Heiko, Sergio,

On Fri, Apr 17 2020, Heiko Thiery wrote:
>> +ASN1C_VERSION = 0.9.28
>> +ASN1C_SITE = https://github.com/vlm/asn1c/releases/download/v$(ASN1C_VERSION)
>
> You can use the github macro to set the <pkg>_SITE variable:
> ASN1C_SITE = $(call github,vlm,asn1c,v$(ASN1C_VERSION))

When the package author provides a tarball we usually prefer to use it.

  If the package you wish to add does have a release section on GitHub,
  the maintainer may have uploaded a release tarball, or the release may
  just point to the automatically generated tarball from the git tag. If
  there is a release tarball uploaded by the maintainer, we prefer to use
  that since it may be slightly different (e.g. it contains a configure
  script so we don?t need to do AUTORECONF).

This is quoted from
https://buildroot.org/downloads/manual/manual.html#github-download-url

In this case the tarball indeed contains a pre-generated configure
script.

baruch

--
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

  parent reply	other threads:[~2020-04-19  3:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 21:14 [Buildroot] [PATCH] package/asn1c: new host package Sergio Prado
2020-02-27  8:54 ` Sergio Prado
2020-04-17 13:28 ` Heiko Thiery
2020-04-17 18:20   ` Sergio Prado
2020-04-19  3:41   ` Baruch Siach [this message]
2020-04-19  5:39     ` Heiko Thiery
2020-04-19 12:47       ` Sergio Prado
2020-09-14 20:41 ` Yann E. MORIN

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=87imhwcfbq.fsf@tarshish \
    --to=baruch@tkos.co.il \
    --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