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 12:45:48 +0100	[thread overview]
Message-ID: <20201101114548.uczKOxCBFPbEWK5ZgzTGvldk8i5B_86PoRhWJC3Clj0@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: 3063 bytes --]

New comment by hippi777 on void-packages repository

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

Comment:
im somewhat dumb to git, but not really, thats not the point, u got mislead by that i am puzzled around it....

those patches only make me understand the difference between the two projects easier, as by simply looking at the ymir repo couldnt help me to figure out their changes. maybe i didnt look hard enough, or it would require some git wizardry to find those 200 packages they patched from that 10k that void has... but this is not the point, this is probably the lack of my education. :D 

the point is that the templates can have optional variations, that is already an existing possibility, and that can be utilized by xbps-src to create the packages either this or that way as a matter of providing a flag (lets say it could even be 'libre' for this case). and the patches they maintain could probably be merged into the original template by utilizing these options. however my problem is that i dont know the scope of these options, while my inner hacker says theres no impossible.

on the contrary, i dunno if _those_ patches that come alongside the templates can be made optional, or they are applied automatically when they present, no matter what. i also dunno if linting (in case of hardcore hacking) or any magic of xbps-src would limit the scope of utilizing those options, and therefore it would prevent bringing anything onto the common ground, that is only about the templates, not the packages.

i think this could be beneficial for both projects, keeping the gap minimal, making the cooperation easier, it maybe even be a step towards a future reunion that we cant even imagine as of now, but here is the power and there is the liberation, and i see that this is a hard nut, but as far as i can think, void has the possibility to include those efforts at the level of the templates, and then the two projects can still do their own different builds.

this was the topic of my previous message.

other than that, that is the original proposal here, is for having templates for whatever stuffs that arent built officially. u can even think about it as a junkyard, where ppl can find their own treasures, that they will maybe need to work on (or maybe not), but at least they will have something to work on and that they dont need to pull out from the thin-air, like even a template for git head grub, that isnt a thing now (in general), cuz it would be a pain to maintain the builds... when someone asked for it, i could search my messy notes.txt for this https://www.reddit.com/r/voidlinux/comments/eo1y08/luks2_support_in_grub/ and i think such materies could get a common ground, and probably it would be the best to keep such gems near to the official templates to be easier to keep them more-or-less in sync with the rest of void, even if they wouldnt get much special care.

and sure, thx for ur patience! i hope i will be able to catch up by the time and become more useful! :D

  parent reply	other threads:[~2020-11-01 11:45 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
2020-11-01 10:29 ` Duncaen
2020-11-01 11:45 ` hippi777 [this message]
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=20201101114548.uczKOxCBFPbEWK5ZgzTGvldk8i5B_86PoRhWJC3Clj0@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).