Github messages for voidlinux
 help / color / mirror / Atom feed
From: hippi777 <hippi777@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [proposal] templates without official binaries
Date: Sun, 01 Nov 2020 10:56:12 +0100	[thread overview]
Message-ID: <20201101095612._b5CXoIZZQE40nyVNmR2dsOyYKXiz66o4_q727CDGIU@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: 2463 bytes --]

New comment by hippi777 on void-packages repository

https://github.com/void-linux/void-packages/issues/25901#issuecomment-720062427

Comment:
ahh, that link pointing to here from ymir made the conversation somewhat tangled, sorry for that! :D probably resolving this and bringing the two conversations to the same ground could make things better, and i guess this place is more straightforward to anything...

so, that notabug repo made the differences much cleaner, i had no idea what else differs other than the kernel, but i knew that there are more things than that... its existence was a great missing link to me, otherwise im aware of the rest, as i have read all the issues of ymir when i found it :D 

> I don't have a lot of experience with big collection of patches. Can it screw things up? Maybe. But this is the solution I have so far.

this is the thing on the very 1st place why i came up with upstreaming there, and the unused templates for things like the libre-kernel here, thinking basically about the templates, and not necessarily the packages, and i guess that actually having an isolated set of patches makes things much smoother, than having only 2 variants of the huge `void-packages` repo heading towards two directions with the possibility of having more and worse conflicts by the time, but im not into git wizardry deep enough to be confident about this, maybe its nothing more complicated than having the patches... otherwise my point was to keep those modifications under options for templates instead in patches, if and whenever its just possible and acceptable.

(((btw sorry for arriving with too much gaps in my knowledge, recently i talked about the awesomenesses of void elsewhere, and then someone showed me guix with its strong points, and told me that it isnt just a matter of not using nonfree to get a libre void, and that made me jumping into this... but still, that tastes like a "scheme fanboy distro" to me that i dont really like, and i think the musl related efforts are probably greater and more important, and moving the strong points of the 2 projects onto the same funds would be better here, as that already have been strongly built around scheme, that wont change any time soon, while picking up musl there seems to be the greater effort, at least by the amount... - but dont mind this, it was just some clearance of my background story, and i really dont want to mess up this topic even more! :D )))

  parent reply	other threads:[~2020-11-01  9:56 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
2020-10-31 17:47 ` reback00
2020-11-01  9:56 ` hippi777 [this message]
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=20201101095612._b5CXoIZZQE40nyVNmR2dsOyYKXiz66o4_q727CDGIU@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).