From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14396] GIthub schema is broken
Date: Sat, 27 Nov 2021 21:12:15 +0000 [thread overview]
Message-ID: <bug-14396-163-XEZWRkchDC@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14396-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14396
--- Comment #2 from Olga <okitain@gmail.com> ---
To save maintainers some trouble, I've been brainstorming how to fix this
issue.
The main problem that I see in this is that the value that should be assigned
to <PACKAGE>_SOURCE and the actual name of the .tar.gz differ. The bluntest
solution is to define <PACKAGE>_SOURCE for each package as something like
release-$(PACKAGE_VERSION).tar.gz, but that means that all mirrors of those
packages will fail and have to be rebuilt.
Instead, maybe $(call github,author,repo,version) should define a fake URI
protocol called github, which allows us to bodge the download process via a new
script located in support/download/github, saving the original <PACKAGE>_SOURCE
definitions while allowing download from unusual URLs that github provides.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-27 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:13 [Buildroot] [Bug 14396] New: GIthub schema is broken bugzilla
2021-11-27 12:03 ` [Buildroot] [Bug 14396] " bugzilla
2021-11-27 20:28 ` bugzilla
2021-11-27 21:12 ` bugzilla [this message]
2021-11-27 21:32 ` bugzilla
2021-11-27 21:54 ` bugzilla
2021-11-27 22:14 ` bugzilla
2021-11-28 8:39 ` bugzilla
2021-11-28 15:52 ` bugzilla
2021-11-28 16:28 ` bugzilla
2021-11-28 16:49 ` bugzilla
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=bug-14396-163-XEZWRkchDC@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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.