all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: mcconnaughey@jeffnet.org
Cc: help-guix@gnu.org
Subject: Re: how to contribute software?
Date: Sat, 17 Oct 2020 12:03:08 +0200	[thread overview]
Message-ID: <87lfg5w4o3.fsf@elephly.net> (raw)
In-Reply-To: <0384dfc54e3593b0bf86bbf0e1c6a815@jeffnet.org>

Hello!

mcconnaughey@jeffnet.org writes:

> My project at experix.sourceforge.net is intended for use in a
> laboratory to operate instruments, collect data from them, analyze and
> present the data graphically, and perform general computations. I am
> interested in making it available […]

Excellent!

> Please give me a little
> guidance on how to package and submit it.

We have a packaging tutorial in the Guix Cookbook:

    https://guix.gnu.org/cookbook/en/html_node/Packaging-Tutorial.html

This covers pretty much everything you may need to know to write a
package definition.

I see in the experix readme file that users are expected to compile the
source files manually with consecutive invocations of GCC.  While that’s
of course possible to express with Guix we usually encounter
applications and libraries that have some sort of build system, e.g. a
Makefile.

When a build system is used Guix packaging becomes really simple as only
one of the existing build system abstractions has to be selected (and
possibly adjusted).  All of the configuration and compilation steps
would be subsumed by a simple declaration like this:

    (build-system gnu-build-system)

Since you are the author of experix you are in a unique position to add
a build system (such as a simple Makefile) to the experix sources.  This
would be preferable over coding the build instructions in Guix (which is
rather verbose for cases like this).

What do you think?

-- 
Ricardo


      parent reply	other threads:[~2020-10-17 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 20:17 how to contribute software? mcconnaughey
2020-10-17  0:33 ` jbranso
2020-10-17 10:03 ` Ricardo Wurmus [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lfg5w4o3.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=mcconnaughey@jeffnet.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.