From: Joshua Branson <jbranso@fastmail.com>
To: guile-user@gnu.org
Subject: Re: How to get started in guile & programming generally
Date: Fri, 31 Aug 2018 10:44:31 -0400 [thread overview]
Message-ID: <87d0ty4muo.fsf@fastmail.com> (raw)
In-Reply-To: <20180831080714.GC7936@tuxteam.de> (tomas's message of "Fri, 31 Aug 2018 10:07:14 +0200")
<tomas@tuxteam.de> writes:
> On Thu, Aug 30, 2018 at 11:42:51PM +0200, Arne Babenhauserheide wrote:
>>
>> Joshua Branson <jbranso@fastmail.com> writes:
>>
>> > It gets really interesting when you start telling these processes to
>> > transform the underlying data. They currently have a translator that
>> > translates an xml file into a directory tree. Imagine searching an html
>> > file with the "find" tool. Wouldn't that be something different?
>>
>> Or imagine installing a packages from remote servers with shell globbing:
>>
>> pkg --install /http://ftp.gnu.org/packages/*/*.deb
>>
>> Last time I used the Hurd, some variant of this actually worked.
>
> Like this (note: my comments interspersed, prefixed with ###)
>
> ### note the option '-s' -- I don't want to clobber my box!
>
> tomas@trotzki:~$ apt-get -s install '*php*'
>
I didn't know that debian support installing all "php" packages like that!
> What's my point?
>
> - Debian has some headstart: it's absolutely worth learning
> from them
What things can guix do like debian does?
> - Perhaps other distros also know how to play this trick
> - Selecting packages by name via some string matching may have
> ummm... strange consequences ;-D
>
> Don't get me wrong: I do think Guix goes into the absolutely right
> direction, as opposed to the current cloudy container craze.
>
> Cheers
> -- tomás
next prev parent reply other threads:[~2018-08-31 14:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 17:16 How to get started in guile & programming generally Joshua Branson
2018-08-25 19:01 ` Amirouche Boubekki
2018-08-25 20:10 ` Pierre Neidhardt
2018-08-25 20:35 ` Matt Wette
2018-08-27 12:39 ` Ludovic Courtès
2018-08-27 13:15 ` Thompson, David
2018-08-26 18:16 ` Joshua Branson
2018-08-26 19:12 ` Pierre Neidhardt
2018-08-27 13:30 ` Thompson, David
2018-08-27 20:42 ` Arne Babenhauserheide
2018-08-29 21:21 ` Joshua Branson
2018-08-29 21:20 ` Joshua Branson
2018-08-29 21:27 ` Amirouche Boubekki
2018-08-30 13:11 ` Joshua Branson
2018-08-30 15:45 ` Amirouche Boubekki
2018-09-03 20:53 ` Joshua Branson
2018-10-19 17:02 ` Joshua Branson
2018-08-30 19:09 ` Arne Babenhauserheide
2018-08-31 11:32 ` Jan Nieuwenhuizen
2018-08-31 15:04 ` Thompson, David
2018-08-31 16:49 ` Jan Nieuwenhuizen
2018-08-31 23:04 ` Ludovic Courtès
2018-08-31 17:45 ` Amirouche Boubekki
2018-08-27 18:46 ` Amirouche Boubekki
2018-08-27 19:08 ` John Cowan
2018-08-29 21:33 ` Joshua Branson
2018-08-30 21:42 ` Arne Babenhauserheide
2018-08-31 8:07 ` tomas
2018-08-31 14:44 ` Joshua Branson [this message]
2018-09-01 10:00 ` Arne Babenhauserheide
2018-09-01 10:49 ` tomas
2018-09-02 23:09 ` Arne Babenhauserheide
2018-08-31 14:42 ` Joshua Branson
2018-08-27 20:54 ` Arne Babenhauserheide
2018-08-29 21:35 ` Joshua Branson
2018-08-30 20:19 ` Arne Babenhauserheide
2018-08-31 14:41 ` Joshua Branson
2018-09-01 10:01 ` Arne Babenhauserheide
2018-09-01 16:26 ` Joshua Branson
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0ty4muo.fsf@fastmail.com \
--to=jbranso@fastmail.com \
--cc=guile-user@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).