From: Alex Kost <alezost@gmail.com>
To: ng0 <ng0@libertad.pw>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: libreoffice: Add 'libreoffice' symlink.
Date: Thu, 08 Dec 2016 12:37:53 +0300 [thread overview]
Message-ID: <871sxidamm.fsf@gmail.com> (raw)
In-Reply-To: <8760mw6b8j.fsf@we.make.ritual.n0.is> (ng0@libertad.pw's message of "Tue, 06 Dec 2016 20:42:04 +0000")
ng0 (2016-12-06 20:42 +0000) wrote:
> Alex Kost <alezost@gmail.com> writes:
[...]
>> I've just noticed that there is 'bin-install' phase right before it, so
>> I think an additional phase is not needed at all, the required
>> symlinking can be done in that 'bin-install' phase.
>
> Okay, I did not want to touch that because I did think for some
> reason it should be separated, but what you provided as diff
> further below looks better than my approach. I'd be okay with
> this. My change is so small, you could probably create your own
> patch and send it to this thread.
Since it's trivial, I committed it¹... but then I realized that
originally it was more like a question about adding 'libreoffice' link
along with the 'soffice' one. So I hope other people will not object
that there is 'bin/libreoffice' now :-)
¹ http://git.savannah.gnu.org/cgit/guix.git/commit/?id=cb72d34348998501c0dfa9f6ac4eb64bddd99fbf
--
Alex
next prev parent reply other threads:[~2016-12-08 9:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 12:25 [PATCH] Add libreoffice symlink to libreoffice ng0
2016-12-05 12:25 ` [PATCH] gnu: libreoffice: Add 'libreoffice' symlink ng0
2016-12-05 12:40 ` Hartmut Goebel
2016-12-05 14:16 ` ng0
2016-12-06 10:42 ` Hartmut Goebel
2016-12-06 18:54 ` Alex Kost
2016-12-06 19:52 ` [PATCH] libreoffice symlink, v2 ng0
2016-12-06 19:52 ` [PATCH] gnu: libreoffice: Add 'libreoffice' symlink ng0
2016-12-06 20:04 ` [PATCH] libreoffice symlink, v3 ng0
2016-12-06 20:04 ` [PATCH] gnu: libreoffice: Add 'libreoffice' symlink ng0
2016-12-06 20:35 ` Alex Kost
2016-12-06 20:42 ` ng0
2016-12-08 9:37 ` Alex Kost [this message]
2016-12-08 22:48 ` 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=871sxidamm.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ng0@libertad.pw \
/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).