From: Erik Edrosa <erik.edrosa@gmail.com>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: a blog post
Date: Fri, 06 Apr 2018 23:35:16 -0400 [thread overview]
Message-ID: <87efjradu3.fsf@gmail.com> (raw)
In-Reply-To: <CAJ98PDwzK4VT5r+8Yk8s=1fwHjV+xf0MzsVzw36RL8N7Dd5HkQ@mail.gmail.com>
Hello Catonano,
Thanks for the blog post, I added your feed to my feed reader. I
understand your frustration with autotools, it can be difficult to
figure out how to get autotools to do what you want. The benefit of
autotools is that it creates the same interface to build, test, and
install GNU software (of course if implemented the correctly...). This
interface usually makes it easier for others to package for their
distribution.
What I think we need to do to improve Guile's chances for success is to
take a serious look at our tools and practices, improve them if needed,
and document the best ways to set up Guile and use it. Guix is great,
but we can't forget Guile users who don't use Guix. This probably
includes packaging Guile libraries for these other package managers.
- Erik (OrangeShark)
next prev parent reply other threads:[~2018-04-07 3:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 8:58 a blog post Catonano
2018-04-06 22:07 ` Autotools formely: " Pjotr Prins
2018-04-09 15:30 ` Guix-based build tool Ludovic Courtès
2018-04-09 15:53 ` julien lepiller
2018-04-11 8:02 ` Catonano
2018-04-16 16:59 ` Christopher Lemmer Webber
2018-04-18 3:50 ` Chris Marusich
2018-04-18 21:06 ` Ludovic Courtès
2018-04-18 21:09 ` Ludovic Courtès
2018-04-19 16:49 ` Catonano
2018-04-20 6:52 ` Catonano
2018-04-20 6:58 ` Catonano
2018-04-23 15:53 ` Ludovic Courtès
2018-04-20 20:13 ` Ricardo Wurmus
2018-04-07 3:35 ` Erik Edrosa [this message]
2018-04-07 9:53 ` a blog post Hartmut Goebel
2018-04-07 10:46 ` Tobias Geerinckx-Rice
2018-04-07 10:59 ` Catonano
2018-04-09 0:18 ` Chris Marusich
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=87efjradu3.fsf@gmail.com \
--to=erik.edrosa@gmail.com \
--cc=catonano@gmail.com \
--cc=guix-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).