unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Adonay Felipe Nogueira via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Re: rust: where is cargo?
Date: Sat, 26 Dec 2020 15:19:42 -0300	[thread overview]
Message-ID: <6402cca4-ae93-928f-bd1b-d149bafbaf2d@hyperbola.info> (raw)
In-Reply-To: <87czywsj92.fsf@nckx>


[-- Attachment #1.1: Type: text/plain, Size: 1978 bytes --]

Em 26/12/2020 12:02, Tobias Geerinckx-Rice escreveu:
>> I know that guix approach is to replace package managers
> 
> I don't think that's true.
It's half true, valid to the extent that, contrary to cargo's default repository, Guix's default follows the GNU FSDG, which also requires that every other repository referenced in that one or by the community also expresses the same commitment. If there is one reference to one which doesn't, then such reference should either be replaced, removed or there must be an agreement between the parties to fix this in the referenced repository.

The act of removing such reference is sometimes done by not including the referrer package, and this is done when there is not much resource left to deal with the fact that other repository must be created.

It's common practice for free/libre system distributions to provide a “GNU FSDG” bug/issue/task tag/section for cases where they provide packages that refer to third-party repositories not committed to the GNU FSDG, along other cases not compliant with GNU FSDG. If cargo is indeed included.


-- 
* 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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2020-12-26 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26 14:34 rust: where is cargo? Todor Kondić
2020-12-26 15:02 ` Tobias Geerinckx-Rice
2020-12-26 18:19   ` Adonay Felipe Nogueira via [this message]
2020-12-26 19:16   ` Adonay Felipe Nogueira via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6402cca4-ae93-928f-bd1b-d149bafbaf2d@hyperbola.info \
    --to=help-guix@gnu.org \
    --cc=adfeno@hyperbola.info \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).