From: ylabidi <ylabidi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: amule-11066
Date: Tue, 08 Dec 2020 02:28:12 +0100 [thread overview]
Message-ID: <20201208012812.9ebCM3cZi8uvPNjI9aW_SlgjswoJrzlmBX1zwzfh4NI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26999@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
New comment by ylabidi on void-packages repository
https://github.com/void-linux/void-packages/pull/26999#issuecomment-740300125
Comment:
I addressed most of the comments:
- used the master branch snapshot with proper checksum instead of a git commit
- converted the build to a `gnu-configure` build style
- removed the restriction to the `x86_64` arch
The lack of tagged release is a deficiency in the upstream project. I think using the import tags from svn is a reasonable replacement for the time being, assuming a regular update schedule.
Let me know if there are other points that need addressing.
next prev parent reply other threads:[~2020-12-08 1:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 21:06 [PR PATCH] " hazayan
2020-12-06 22:40 ` hazayan
2020-12-06 22:52 ` Duncaen
2020-12-06 23:16 ` hazayan
2020-12-06 23:17 ` hazayan
2020-12-06 23:25 ` Duncaen
2020-12-06 23:28 ` hazayan
2020-12-08 1:21 ` [PR PATCH] [Updated] " hazayan
2020-12-08 1:28 ` ylabidi [this message]
2020-12-08 2:47 ` ylabidi
2020-12-08 3:32 ` fosslinux
2020-12-08 11:44 ` [PR REVIEW] " Duncaen
2020-12-08 11:46 ` Duncaen
2020-12-08 11:47 ` Duncaen
2020-12-08 11:47 ` Duncaen
2020-12-08 11:48 ` Duncaen
2020-12-09 1:57 ` [PR PATCH] [Updated] " hazayan
2020-12-09 1:58 ` [PR REVIEW] " ylabidi
2020-12-09 1:59 ` ylabidi
2020-12-09 2:01 ` ylabidi
2020-12-09 2:01 ` ylabidi
2020-12-09 2:02 ` ylabidi
2020-12-09 2:03 ` ylabidi
2020-12-09 2:04 ` ylabidi
2020-12-09 2:09 ` ylabidi
2020-12-09 23:06 ` Piraty
2020-12-09 23:11 ` Piraty
2020-12-09 23:14 ` ylabidi
2020-12-09 23:14 ` Duncaen
2020-12-09 23:16 ` [PR REVIEW] " ylabidi
2020-12-09 23:17 ` ylabidi
2020-12-09 23:17 ` ylabidi
2020-12-09 23:18 ` ylabidi
2020-12-09 23:18 ` ylabidi
2020-12-09 23:18 ` ylabidi
2020-12-09 23:20 ` hazayan
2020-12-09 23:25 ` Duncaen
2020-12-09 23:30 ` hazayan
2020-12-09 23:30 ` hazayan
2020-12-09 23:42 ` [PR PATCH] [Updated] " hazayan
2020-12-09 23:42 ` [PR REVIEW] " hazayan
2020-12-09 23:43 ` hazayan
2020-12-09 23:59 ` [PR PATCH] [Updated] New package: amule-0.0.20201210 hazayan
2021-02-28 3:00 ` hazayan
2021-03-04 20:30 ` Piraty
2021-06-14 20:00 ` Piraty
2022-05-01 2:14 ` github-actions
2022-05-16 2:07 ` [PR PATCH] [Closed]: " github-actions
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=20201208012812.9ebCM3cZi8uvPNjI9aW_SlgjswoJrzlmBX1zwzfh4NI@z \
--to=ylabidi@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).