From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Cc: 25273@debbugs.gnu.org
Subject: Re: midnight commander package fixes, opinions wanted
Date: Mon, 6 Mar 2017 11:09:43 +0000 [thread overview]
Message-ID: <20170306110942.bg4rdzesgqlrx7kq@abyayala> (raw)
In-Reply-To: <20170301170123.37y4d36dziq6ewqo@abyayala>
On 17-03-01 17:01:23, 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.
>
For the lack of reaction for a long time, due to whatever reasons, I
will simply propose that we go the way of vim and vim-full.
'mc-full' will have many more dependencies than our current 'mc' and
should in the end be fully functional, while 'mc' will still complain
about missing features. The description of mc-full shall reflect that
you get full functionality with this application variant.
Anyone who wants this, feel free to pick it up and fix the related bug.
prev parent reply other threads:[~2017-03-06 10:01 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
2017-03-06 11:14 ` ng0
2017-03-06 11:09 ` ng0 [this message]
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=20170306110942.bg4rdzesgqlrx7kq@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=25273@debbugs.gnu.org \
--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).