From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: 2 ideas Date: Sun, 10 Jun 2018 13:45:32 +0200 Message-ID: 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> <87bmcjnm6t.fsf@gmail.com> <87wov7nezw.fsf@gmail.com> <04ad5f85-fa47-b89c-4ae5-a15c05a5059f@freenet.de> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a8bbb8056e482b54" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43932) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fRymu-0003wR-61 for guix-devel@gnu.org; Sun, 10 Jun 2018 07:45:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fRymt-0001WE-15 for guix-devel@gnu.org; Sun, 10 Jun 2018 07:45:36 -0400 Received: from mail-it0-x22c.google.com ([2607:f8b0:4001:c0b::22c]:35691) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fRyms-0001UD-RU for guix-devel@gnu.org; Sun, 10 Jun 2018 07:45:34 -0400 Received: by mail-it0-x22c.google.com with SMTP id a3-v6so7773528itd.0 for ; Sun, 10 Jun 2018 04:45:33 -0700 (PDT) In-Reply-To: <04ad5f85-fa47-b89c-4ae5-a15c05a5059f@freenet.de> 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: Thorsten Wilms Cc: Guix-devel --000000000000a8bbb8056e482b54 Content-Type: text/plain; charset="UTF-8" 2018-06-10 13:26 GMT+02:00 Thorsten Wilms : > On 10.06.2018 11:54, Pierre Neidhardt wrote: > >> Then intention of the Arch post-install script is good (that is, >> informing the user) but I find the implementation brittle: if the >> messages are too many or too long, it can be very easy to miss a >> message. >> >> Furthermore, the script cannot be triggered out-of-install, which means >> that once the shell session is gone, the information is gone. (It's >> still in the log but it's not so convenient to read and you must know >> what you are looking for in advance.) >> > > > What if each package with such a message would install it as a text-file > in a specific directory? With a separate mechanism to bring each new > message file to the user's attention, plus a means of stepping through all > of them. > > > I think it might be nice to have something like --show-post-install-doc in guix package, if we decide to implement this.++ > -- > Thorsten Wilms > > thorwil's design for free software: > http://thorwil.wordpress.com/ > > --000000000000a8bbb8056e482b54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2018= -06-10 13:26 GMT+02:00 Thorsten Wilms <t_w_@freenet.de>:
On 10.06.2018 11:54, Pierre N= eidhardt wrote:
Then intention of the Arch post-install script is good (that is,
informing the user) but I find the implementation brittle: if the
messages are too many or too long, it can be very easy to miss a
message.

Furthermore, the script cannot be triggered out-of-install, which means
that once the shell session is gone, the information is gone.=C2=A0 (It'= ;s
still in the log but it's not so convenient to read and you must know what you are looking for in advance.)


 What if each package with such a message would install it as a text-file in= a specific directory? With a separate mechanism to bring each new message = file to the user's attention, plus a means of stepping through all of t= hem.



I think it might be nice= to have something like --show-post-install-doc in guix package, if we deci= de to implement this.++
=C2=A0
--
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/


--000000000000a8bbb8056e482b54--