From: hippi777 <hippi777@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [proposal] templates without official binaries
Date: Sat, 31 Oct 2020 18:23:08 +0100 [thread overview]
Message-ID: <20201031172308.Z27gXFniIi__8GsYWuZZz_rEy7-CdcvywAFapBfGLjM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25901@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
New comment by hippi777 on void-packages repository
https://github.com/void-linux/void-packages/issues/25901#issuecomment-719962998
Comment:
thx for u too! now i have a way better understanding about what im facing with! :)
and yes, i was thinking about fsdg, i think its the right time to read more about both them, not that i would be lazy, but that i always have more things to learn/do than what i actually can :D
> were refused because their default repo has some nonfree parts or they host the nonfree repo on their own server.
this already makes the nonfree case reasonable, next time i will try to be smarter! :)
otherwise the common ground for the templates could still be nice, but im also under educated about the requirements of this, and i hope i will catch up with things around here sooner than later :D
next prev parent reply other threads:[~2020-10-31 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 15:53 [ISSUE] " hippi777
2020-10-27 11:53 ` Duncaen
2020-10-27 11:53 ` Duncaen
2020-10-27 13:20 ` hippi777
2020-10-31 16:58 ` reback00
2020-10-31 17:23 ` hippi777 [this message]
2020-10-31 17:47 ` reback00
2020-11-01 9:56 ` hippi777
2020-11-01 10:29 ` Duncaen
2020-11-01 11:45 ` hippi777
2020-11-01 12:05 ` Duncaen
2020-11-01 12:06 ` Duncaen
2020-11-01 18:13 ` reback00
2020-11-01 18:14 ` reback00
2020-11-01 18:17 ` reback00
2020-11-01 20:06 ` hippi777
2020-11-01 22:31 ` fosslinux
2020-11-01 22:34 ` fosslinux
2020-11-02 16:12 ` reback00
2022-04-22 2:14 ` github-actions
2022-04-22 15:56 ` [ISSUE] [CLOSED] " Duncaen
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=20201031172308.Z27gXFniIi__8GsYWuZZz_rEy7-CdcvywAFapBfGLjM@z \
--to=hippi777@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).