Hi, Thanks for taking the time to respond. Sounds like good news overall....
On Wed, May 20, 2020 at 6:57 AM zimoun <zimon.touto...@gmail.com> wrote: > > Hi Ricardo, > > On Wed, 20 May 2020 at 13:02, Ricardo Wurmus <rek...@elephly.net> wrote: > > > I expect that this will change soon after some more discussion of the > > details. > > Last time we discussed that was on December [1]. What is missing is: discuss > if > > a) an "official" mirror is hard-coded in '%default-channels' > or > b) an "official" mirror is documented in the manual and it is up to > the user to setup it via ~/.config/guix/channels.scm. > > The a) annoys people who do not want the mirror, so they have to tweak > the list by themself and in the same a) is more newcomer-friendly > because it just works. > The b) annoys newcomers because it is another step and in the same > time b) is more customizable. > > Obviously, there is option c): guix-install.sh asks a question and > then do the b) dance. > > > And discuss if a channel is described as: > > (channel > (name 'guix) > (url "https://savannah…";) > (mirror (list "https://mirror-one…"; > "https://mirror-two…";))) > > [ where mirror is optional ] > > or something else? There should be a built in (hard-coded) failover list - ideally three - without the user being told or asked to do anything during setup. Ideally the user could alter that list - but that seems a stage 2 feature given the curent state. Stage 3 might alllow the default list to vary by country code - driven by and env var set to two letter ISO code? I was surprised guix doesn't seem to be mirrored to gnu.io - or is that the same machine(s)? On reflection in this context 'mirror' is not descriptive in the channel config - 'failover' might better communicate the intent and context (channel (name 'guix) (url "https://savannah…";) (failover (list (url "https://mirror-one…";) (url "https://mirror-two…";)))) where **overriding** the failover list is optional, but you cannot unset the default list HTH > Well, Ludo suggested [2] to address "Trustable guix pull" [3]; which > should be really cool! > Now, I am not sure to understand if there is no mirror mechanism > because no one took the time to implement it or if any other reasons > related to "trustable guix pull". > > > [1] https://lists.gnu.org/archive/html/guix-devel/2019-12/msg00150.html > [2] https://lists.gnu.org/archive/html/guix-devel/2019-12/msg00276.html > [3] http://issues.guix.gnu.org/issue/22883 > > > Cheers, > simon -- Kind Regards Begley Brothers Inc. The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. This message has been sent as a part of discussion between Begley Brothers Inc. and the addressee whose name is specified above. Should you receive this message by mistake, we would be most grateful if you informed us that the message has been sent to you. In this case, we also ask that you delete this message from your mailbox, and do not forward it or any part of it to anyone else. Thank you for your cooperation and understanding. Begley Brothers Inc. puts the security of the client at a high priority. Therefore, we have put efforts into ensuring that the message is error and virus-free. Unfortunately, full security of the email cannot be ensured as, despite our efforts, the data included in emails could be infected, intercepted, or corrupted. Therefore, the recipient should check the email for threats with proper software, as the sender does not accept liability for any damage inflicted by viewing the content of this email. The views and opinions included in this email belong to their author and do not necessarily mirror the views and opinions of the company. Our employees are obliged not to make any defamatory clauses, infringe, or authorize infringement of any legal right. Therefore, the company will not take any liability for such statements included in emails. In case of any damages or other liabilities arising, employees are fully responsible for the content of their emails.
