From: reback00 <reback00@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: Sunflower 0.4 (62)
Date: Mon, 05 Oct 2020 12:06:12 +0200 [thread overview]
Message-ID: <20201005100612.8Cv4H7pVVqYTpC-5SsLpFfc40aY9jQhTa9rBw7Znbf8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25062@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
New comment by reback00 on void-packages repository
https://github.com/void-linux/void-packages/issues/25062#issuecomment-703534009
Comment:
@gorkawien OK, good template you got there. Especially, I like the `version` value being set to `0.4.62`. Makes better sense than mine.
But it seems on your template it will need `python3-setuptools` on `hostdepends`. And possibly it will need some more depends after that. I got them solved in mine. I don't have any build errors. But the problem seems to be that some changes are not updated in master yet for it to work in Void Linux.
As [suggested](https://github.com/MeanEYE/Sunflower/issues/453#issuecomment-703146876) by the author, I tried their `develop` branch and it [partially worked](https://github.com/MeanEYE/Sunflower/issues/453#issuecomment-703181779). I think the path error that I got in develop branch, is fixable through a patch to the source code (even if they don't push any changes for that). But can we push a develop branch package to void-packages repo? I don't think it will be accepted. I think this will be a problem if the changes are not merged to master soon.
next prev parent reply other threads:[~2020-10-05 10:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 22:49 [ISSUE] " gorkawien
2020-10-03 17:57 ` reback00
2020-10-03 20:56 ` gorkawien
2020-10-04 8:04 ` gorkawien
2020-10-05 10:06 ` reback00 [this message]
2020-10-05 11:07 ` gorkawien
2020-10-05 11:39 ` reback00
2020-10-06 16:39 ` gorkawien
2020-10-06 16:53 ` gorkawien
2020-10-07 19:56 ` reback00
2020-10-08 10:39 ` gorkawien
2020-10-09 5:19 ` reback00
2021-06-08 0:56 ` bugcrazy
2023-05-10 17:00 ` niels0n
2023-05-10 21:07 ` bugcrazy
2023-05-10 23:05 ` niels0n
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=20201005100612.8Cv4H7pVVqYTpC-5SsLpFfc40aY9jQhTa9rBw7Znbf8@z \
--to=reback00@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).