From: Jesse Gibbons <jgibbons2357@gmail.com>
To: "Pierre Neidhardt" <mail@ambrevar.xyz>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: New build system: copy-build-system
Date: Mon, 17 Feb 2020 09:52:29 -0700 [thread overview]
Message-ID: <1ed7675e6db59c6c7bb7c53bf214ad1b7a7d74ca.camel@gmail.com> (raw)
In-Reply-To: <877e0ltzo6.fsf@ambrevar.xyz>
On Mon, 2020-02-17 at 08:56 +0100, Pierre Neidhardt wrote:
> Error verifying signature: Failed to execute gpg.
> Hi Jesse,
>
> thanks for sharing, I'll include it with the patch then.
>
> > Since I'm patching one of the scripts to play better with guix, the
> > source will become a tarball. I would rather not worry about
> > extracting
> > everything, moving some things, and deleting what is not used.
>
> What do you mean with this?
>
Sorry if I confused you.
The package I shared will need to be adjusted because I'm not sure how
to configure the copy-build-system. It was also in an early stage, and
the source itself will need some changes for the package to work. I
only sent it to help you test copy-build-system, since you asked for
suggestions.
The package as I sent it, even if changed to use the copy-build-system,
is not ready to be sent to to guix because it will not find java or the
clojure jar built by guix. I already have a patch to correct this, and
intend to send it with the rest of the package when I can call
"clojure" from bash in an pure environment with the clojure package and
enter a clojure repl.
IIUC, copy-build-system is based on gnu-build-system, so it should work
the same with tarballs and directories. That means it should be a time
saver; I won't need to worry about changing things if I need to add a
patch to make a package work with what guix does. Thank you so much for
this build system :)
-Jesse
next prev parent reply other threads:[~2020-02-17 16:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 20:27 New build system: copy-build-system Pierre Neidhardt
2020-01-27 0:45 ` Jesse Gibbons
2020-01-27 4:14 ` Jack Hill
2020-01-27 14:27 ` zimoun
2020-01-27 14:44 ` Pierre Neidhardt
2020-01-27 15:03 ` zimoun
2020-01-27 15:18 ` Pierre Neidhardt
2020-01-27 15:36 ` zimoun
2020-01-27 15:51 ` Pierre Neidhardt
2020-01-27 16:17 ` zimoun
2020-01-27 18:18 ` Julien Lepiller
2020-01-27 16:45 ` How to deal with very large sources Ricardo Wurmus
2020-01-27 19:03 ` New build system: copy-build-system Ricardo Wurmus
2020-01-28 10:32 ` Ludovic Courtès
2020-01-28 13:39 ` Pierre Neidhardt
2020-01-28 23:04 ` Ludovic Courtès
2020-02-14 12:54 ` Pierre Neidhardt
2020-02-14 13:22 ` Julien Lepiller
2020-02-17 3:46 ` Jesse Gibbons
2020-02-17 7:56 ` Pierre Neidhardt
2020-02-17 16:52 ` Jesse Gibbons [this message]
2020-02-17 17:10 ` Pierre Neidhardt
2020-02-19 1:33 ` Alex Griffin
2020-02-19 14:01 ` Pierre Neidhardt
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=1ed7675e6db59c6c7bb7c53bf214ad1b7a7d74ca.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
/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).