unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Nils Gillmann <ng0@n0.is>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: 2 ideas (Was: Re: bug#31518: [PATCH 10/21] gnu: Add emacs-google-translate.)
Date: Sun, 10 Jun 2018 13:35:00 +0200	[thread overview]
Message-ID: <87o9gizxgb.fsf@elephly.net> (raw)
In-Reply-To: <20180609111751.rvm54ouwwr4wz7lo@abyayala>


Hi Nils,

> I think we discussed something similar briefly. Or at least package
> attached metadata which ends up in a '/guix' folder of the output.
> I've been following (not yet implementing) a similar idea, where
> such messages are either local mail and/or end up in a (mapped to guix:)
> '/guix/doc/' folder, where files are named like $applicationname-$version.number.NAME.note
> where '.note' is just a basic txt file.
> These notes could contain messages specific to the OS, the architecture, general
> advice, etc.
>
> Not really well thought through yet, but that's a start.
>
> Think of it not as description or synopsis part, but rather let's say
> (in theory):
> (note "STRING") or (note (list "NOTE 1"
>                                "NOTE 2")).

This is not a bad idea, in my opinion.  It could be useful to have
application-specific setup notes in a well-known location that is
gathered when the profile is built.

I would not like these notes to be printed automatically upon
installation, but generating a file with important notes seems like a
good idea in general.

--
Ricardo

  parent reply	other threads:[~2018-06-10 11:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180518184910.9987-21-ambrevar@gmail.com>
     [not found] ` <20180601075112.28494-1-ambrevar@gmail.com>
     [not found]   ` <87vaatjptt.fsf@gnu.org>
2018-06-09  9:12     ` 2 ideas (Was: Re: bug#31518: [PATCH 10/21] gnu: Add emacs-google-translate.) swedebugia
2018-06-09 11:17       ` Nils Gillmann
2018-06-10  7:19         ` 2 ideas Chris Marusich
2018-06-10  9:54           ` Pierre Neidhardt
2018-06-10 11:26             ` Thorsten Wilms
2018-06-10 11:45               ` Gábor Boskovits
2018-06-10 11:35         ` Ricardo Wurmus [this message]
2018-06-10 13:42           ` 2 ideas (Was: Re: bug#31518: [PATCH 10/21] gnu: Add emacs-google-translate.) swedebugia
2018-06-10 14:16             ` Nils Gillmann
2018-06-11  5:18           ` 2 ideas Chris Marusich
2018-06-11  7:40             ` Nils Gillmann

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=87o9gizxgb.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=ng0@n0.is \
    /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).