From: Efraim Flashner <efraim@flashner.co.il>
To: guix-devel@gnu.org
Subject: Re: midnight commander package fixes, opinions wanted
Date: Mon, 6 Mar 2017 11:55:27 +0200 [thread overview]
Message-ID: <20170306095527.GA23203@macbook42.flashner.co.il> (raw)
In-Reply-To: <20170301170123.37y4d36dziq6ewqo@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Wed, Mar 01, 2017 at 05:01:23PM +0000, ng0 wrote:
> On 17-03-01 16:58:41, ng0 wrote:
> > Hi,
> >
> > I already fixed some of the open issues with our package of 'mc'.
> >
> > I think people will expect features to just work and not being broken
> > (as they are right now).
> > My personal opinion ignored, how do you want to proceed? The vim way
> > where we have $package (basic, as small as it gets) and $package-full
> > (with all the features you can have enabled)?
> >
> > I'd like to hear your opionion so that I can proceed fixing mc with
> > what we agreed on.
> >
>
> And also your opinion, I don't know what an opionion is but it sounds
> like opium combined with onion and I don't want that.
>
I've been sitting on a patch for ranger for a while. I also couldn't
decide between packaging just ranger or also linking in the various
programs it calls.
I think that if mc would use libcaca to display an image, and just
installing libcaca in profile would satisfy that dependancy, then
leaving it out is "not great, but acceptable".
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-06 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 16:58 midnight commander package fixes, opinions wanted ng0
2017-03-01 17:01 ` ng0
2017-03-06 9:55 ` Efraim Flashner [this message]
2017-03-06 11:14 ` ng0
2017-03-06 11:09 ` ng0
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=20170306095527.GA23203@macbook42.flashner.co.il \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/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).