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: Tue, 27 Oct 2020 14:20:55 +0100	[thread overview]
Message-ID: <20201027132055.qavzyy7VjDo_V8PWy0gOcHqZqgXLGeY0JfWStAKjOL4@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: 2293 bytes --]

New comment by hippi777 on void-packages repository

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

Comment:
ohh, thx, i see! :)

so, if i understood correctly, then there are some missing bits without actually running the functions inside the templates, and the info that can be obtained from the variables are insufficient, and its still not a real solution to not make actual packages but something similar with whatever info that can be obtained from the templates...

this way, i can think about 3 possibilities, or 4:

the 1st is to have them only for having a template that either works or not, but its already written and those who want to make use of it, will still need to test it on their own, but they wont need to write it from the ground up, and there is nothing much to do about these other than letting them exists with some isolation or denotation as such.

the 2nd is to get the actual metadata from those that will actually use them (maybe alongside their identity and environment), as actually running them is the missing link, and then the integrity checks can be done, while it is only reliable at this level, but not that these or things relying on them will really work, and in the worst case (mistake or bad intention) it just wont actually work. whoever would use such should be aware of this, but its still better than hunting for templates in the wild or doing it alone.

the 3rd possibility, is that if the infra, as a bottleneck, is the only showstopper, then it is to ask the community to pay for some upgrades, and i think it would work and render void that much more competitive.

the 4th is the sad path, that is letting void get fragmented by those who want to resolve common needs elsewhere, like how ymir-linux became a thing (that i found after my message :D ), that really isnt in a shiny state as of now, and i think i only saw 2 ppl there, but its about nothing that really requires a spin-off, while it could be really a strong selling point for void. (((btw i saw on the way that the ryf cert has even more crazy requirements, like the nonfree repo couldnt even exists... X'D but whatever, if void can be used without blobs with official support, then it can be advertised as such without a ryf cert.)))

  parent reply	other threads:[~2020-10-27 13:20 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 [this message]
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
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=20201027132055.qavzyy7VjDo_V8PWy0gOcHqZqgXLGeY0JfWStAKjOL4@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).