Em 05/03/2021 16:20, Vinícius dos Santos Oliveira escreveu:
> You don't want to be a slave to upstream developers' decisions and
> want to apply out-of-tree patches that automatically propagate to the
> rest of the packages ecosystem.

I don't know the specifics of the non-free software Nix, but by experience I think that one of those might suit your case:

a) the (package (source (origin (patches …) …) …) …) definition, where stuff is applied right after being unpacked/extracted, before configuring and building. If you are dealing with GNU FSDG issues or things which will be upstreamed, this would be the perfect place for the patch since you wouldn't be forcing the source package to use Guix's store paths or Guix-specific changes. It also means that people who do guix build -S will receive the source with patches applied;

b) an invocation of GNU patch from (package (arguments (modify-phases …) …) …), allowing you to do as (a) but for Guix-specific changes;

c) use of (package (replacement …) …) to your own package definitions to provide grafts (see `info guix "Security Updates" ` for the requirements and caveats), but note that, since I don't use this option, I don't know much about how to implement it;

d) invoking guix build — or those with support for its transformation options — with --with-patches=PACKAGE=FILE, to do it like (a);

e) same as (d), but with --with-grafts=PACKAGE=REPLACEMENT, to do it like (c);

f) same as (d), but with --with-latest=PACKAGE, to force a given build/install/upgrade to use the latest known version of PACKAGE instead of the one from the built package's definition. This of course comes at a price, as can be read on `info guix "Package Transformation Options" `


-- 
* Ativista do software livre
	* https://libreplanet.org/wiki/User:Adfeno
	* Membro dos grupos avaliadores de
		* Software (Free Software Directory)
		* Distribuições de sistemas (FreedSoftware)
		* Sites (Free JavaScript Action Team)
	* Não sou advogado e não fomento os não livres
* Sempre veja o spam/lixo eletrônico do teu e-mail
	* Ou coloque todos os recebidos na caixa de entrada
* Sempre assino e-mails com OpenPGP
	* Chave pública: vide endereço anterior
	* Qualquer outro pode ser fraude
	* Se não tens OpenPGP, ignore o anexo "signature.asc"
* Ao enviar anexos
	* Docs., planilhas e apresentações: use OpenDocument
	* Outros tipos: vide endereço anterior
* Use protocolos de comunicação federadas
	* Vide endereço anterior
* Mensagens secretas somente via
	* XMPP com OMEMO
	* E-mail criptografado e assinado com OpenPGP