From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus 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 Message-ID: <87o9gizxgb.fsf@elephly.net> References: <20180518184910.9987-21-ambrevar@gmail.com> <20180601075112.28494-1-ambrevar@gmail.com> <87vaatjptt.fsf@gnu.org> <8C242137-C737-4814-9367-6C90F5E96CD2@riseup.net> <20180609111751.rvm54ouwwr4wz7lo@abyayala> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42638) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fRyd4-0002Gr-JR for guix-devel@gnu.org; Sun, 10 Jun 2018 07:35:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fRyd1-0006PS-A4 for guix-devel@gnu.org; Sun, 10 Jun 2018 07:35:26 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21077) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fRyd0-0006Os-On for guix-devel@gnu.org; Sun, 10 Jun 2018 07:35:23 -0400 In-reply-to: <20180609111751.rvm54ouwwr4wz7lo@abyayala> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Nils Gillmann Cc: Guix-devel 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