From: Ricardo Wurmus <rekado@elephly.net>
To: alex.sassmannshausen@gmail.com
Cc: Arne Babenhauserheide <arne_bab@web.de>,
guile-devel <guile-devel@gnu.org>
Subject: Re: FOSDEM 2019
Date: Wed, 06 Feb 2019 22:03:15 +0100 [thread overview]
Message-ID: <87o97ofx4c.fsf@elephly.net> (raw)
In-Reply-To: <87mun8ditj.fsf@gmail.com>
Alex Sassmannshausen <alex.sassmannshausen@gmail.com> writes:
> Hi Amirouche
>
> Amirouche Boubekki writes:
>
>> Le mer. 6 févr. 2019 à 14:47, Alex Sassmannshausen <alex.sassmannshausen@gmail.com> a écrit :
>>
>> > - Janneke mentioned the new guile build system in guix for simpler
>> > guile packages and I think that's pretty great. Likewise there was
>> > some mention of some sort of you-don't-have-to-use-autotools build
>> > system and I don't remember what it's name was. (BTW, I continue to
>> > believe that "Guix is and should be Guile's package mangager".)
>>
>> I was unaware that we had a guile build system in Guix.
>>
>> What is it?
>
> I may be misunderstanding — so feel free to clarify!
>
> The build system in Guix would be a value that can be declared in the
> `build-system' field of package definitions. It's basically what tells
> Guix what steps need to be performed to build and install an
> application.
>
> Guile libraries and applications currently need to use the GNU Build
> System, or the trivial build system, with some additional steps that
> need to be added by the packager.
>
> If we had a build system, we could simply stick the `guile-build-system'
> value in the `build-system' field.
This exists. I use it for the picture language, for example. Here’s
the Guix definition:
--8<---------------cut here---------------start------------->8---
(define-public guile-picture-language
(let ((commit "1531116036d1b5e0d2482ff2c8d77ad21f1d2bef")
(revision "1"))
(package
(name "guile-picture-language")
(version (git-version "0" revision commit))
(source (origin
(method git-fetch)
(uri (git-reference
(url "https://git.elephly.net/software/guile-picture-language.git")
(commit commit)))
(sha256
(base32
"04salmqf5x84vb3qkkxx47b64jyl290zsf3ik81l9hg6fwvvlmq3"))))
(build-system guile-build-system)
(inputs
`(("guile" ,guile-2.2)))
(home-page "https://git.elephly.net/software/guile-picture-language.git")
(synopsis "Picture language for Guile")
(description
"This package provides a simple SVG-based picture language for Guile.
The picture values can directly be displayed in Geiser.")
(license license:lgpl3+))))
--8<---------------cut here---------------end--------------->8---
This takes care of compiling the files and placing them where they
should go. The upstream picture language repository does not use
Autotools.
--
Ricardo
next prev parent reply other threads:[~2019-02-06 21:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 21:34 FOSDEM 2019 Mikael Djurfeldt
2019-02-03 23:13 ` Arne Babenhauserheide
2019-02-04 5:21 ` Nala Ginrut
2019-02-05 21:25 ` Christopher Lemmer Webber
2019-02-06 13:46 ` Alex Sassmannshausen
2019-02-06 15:22 ` Amirouche Boubekki
2019-02-06 15:33 ` Amirouche Boubekki
2019-02-06 15:42 ` Alex Sassmannshausen
2019-02-06 21:03 ` Ricardo Wurmus [this message]
2019-02-06 22:09 ` Alex Sassmannshausen
2019-02-26 8:57 ` swedebugia
2019-02-06 20:40 ` Arne Babenhauserheide
2019-02-05 21:26 ` Christopher Lemmer Webber
2019-02-04 13:06 ` Amirouche Boubekki
2019-02-04 14:44 ` Ludovic Courtès
2019-02-04 18:01 ` Jan Nieuwenhuizen
2019-02-05 11:09 ` Amirouche Boubekki
2019-02-05 16:58 ` Ludovic Courtès
2019-02-06 0:31 ` Nala Ginrut
2019-02-06 12:59 ` Ludovic Courtès
2019-02-06 19:09 ` Amirouche Boubekki
2019-02-06 0:37 ` Matt Wette
2019-02-06 0:56 ` Nala Ginrut
2019-02-06 1:40 ` Amirouche Boubekki
2019-02-05 2:30 ` Matt Wette
-- strict thread matches above, loose matches on Subject: below --
2018-08-21 13:33 Manolis Ragkousis
2018-08-21 17:57 ` Ricardo Wurmus
2018-08-22 16:27 ` Andy Wingo
2018-08-22 2:33 ` Mike Gran
2018-08-23 0:08 ` Mike Gran
2018-08-24 12:23 ` Christopher Lemmer Webber
2018-08-29 21:08 ` Ludovic Courtès
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=87o97ofx4c.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=alex.sassmannshausen@gmail.com \
--cc=arne_bab@web.de \
--cc=guile-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.
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).