unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Robert Vollmert <rob@vllmrt.net>, guix-devel@gnu.org
Subject: Re: distinguishing between applications and libraries
Date: Sun, 30 Jun 2019 20:01:35 +0200	[thread overview]
Message-ID: <874l47hs00.fsf@ambrevar.xyz> (raw)
In-Reply-To: <0E655A03-834C-4219-8956-D69CF4C6A444@vllmrt.net>

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

Hi Robert!

`guix search` and other user-facing tools ignore non-exported packages.

So you can simply use `define` instead of `define-public` to declare a
package.

For instance:

--8<---------------cut here---------------start------------->8---
(define my-package
  ...
  )
--8<---------------cut here---------------end--------------->8---

> - maybe there’s some other simplifications to make in library
>   package definitions? I’d be happy to not copy over a
>   long description that no-one’s ever going to read. :)

The description does not have to be long, in fact it can be just one
line, but it just explain what the package is here for.  Even if it is
not exposed to the user, package maintainers will want to know why it's
here.

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-06-30 18:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-30 17:33 distinguishing between applications and libraries Robert Vollmert
2019-06-30 18:01 ` Pierre Neidhardt [this message]
2019-06-30 20:05   ` Robert Vollmert
2019-06-30 21:20     ` Pierre Neidhardt
2019-07-01 21:46       ` Ricardo Wurmus
2019-07-01 22:02         ` Pierre Neidhardt
2019-07-02  6:51           ` Ricardo Wurmus
2019-07-02  0:24     ` Jakob L. Kreuze
2019-07-02  6:55       ` Ricardo Wurmus
2019-07-02 15:24         ` Jakob L. Kreuze
2019-07-01  8:30 ` Danny Milosavljevic
2019-07-01 11:29   ` Pierre Neidhardt
2019-07-01 21:48 ` Ricardo Wurmus
2019-07-02 13:35   ` Robert Vollmert
2019-07-02 14:33     ` zimoun
2019-07-05 20:58 ` 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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=874l47hs00.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=rob@vllmrt.net \
    /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).