unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Miles Fidelman <mfidelman@meetinghouse.net>
To: help-guix@gnu.org
Subject: Re: good overview presentation?
Date: Thu, 9 May 2019 17:42:39 -0400	[thread overview]
Message-ID: <2f3da087-041c-8053-69e7-d69ed3c034d4@meetinghouse.net> (raw)
In-Reply-To: <875zqjoa3k.fsf@cbaines.net>

Thanks Chris,

A couple of follow-ups:

On 5/9/19 12:39 PM, Christopher Baines wrote:
>
> 1: http://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/talks
>
> There's also two talks [2] which I've given in the past on Guix, they're
> a few years old, but I think most of the material is still correct.
>
Silly me, but how does one view these things?  The ones labeled with 
.pdf extensions come across as ascii files, that can't be read as pdf, 
and others look like they have to be assembled.

These are pretty good, and helpful - but they do raise a key question:


> 2: https://www.cbaines.net/projects/guix/
>
> The FOSDEM 2018 one is shorter, and higher level [3].
>
> 3: https://www.cbaines.net/projects/guix/fosdem-2018/presentation/#/
>
> The Freenode live! 2017 one is longer and more technical [4].
>
> 4: https://www.cbaines.net/projects/guix/freenode-live-2017/presentation/#/

 From the slides, it looks like GUIX keeps track of dependencies, but 
there's no discussion about how dependencies are identified, included in 
the package definitions, or resolved at install time. Details (or 
pointer) please!

Thanks Again,

Miles



-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra

Theory is when you know everything but nothing works.
Practice is when everything works but no one knows why.
In our lab, theory and practice are combined:
nothing works and no one knows why.  ... unknown

  reply	other threads:[~2019-05-09 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 15:04 good overview presentation? Miles Fidelman
2019-05-09 16:39 ` Christopher Baines
2019-05-09 21:42   ` Miles Fidelman [this message]
2019-05-10  7:15     ` Christopher Baines
2019-05-10  7:37     ` Giovanni Biscuolo
2019-05-10 12:57       ` sirgazil
2019-05-10 16:15         ` thanks all - for answers to recent questions Miles Fidelman

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=2f3da087-041c-8053-69e7-d69ed3c034d4@meetinghouse.net \
    --to=mfidelman@meetinghouse.net \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).