public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marijn Schouten (hkBst)" <hkBst@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: compnerd@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-editors/leafpad: ChangeLog leafpad-0.8.14.ebuild
Date: Mon, 31 Mar 2008 08:26:40 +0200	[thread overview]
Message-ID: <47F08420.70705@gentoo.org> (raw)
In-Reply-To: <200803301323.05512.vapier@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Frysinger wrote:
| On Sunday 30 March 2008, Ulrich Mueller wrote:
|>>>>>> On Sun, 30 Mar 2008, Mike Frysinger wrote:
|>>> And IMHO the "emacs" USE flag should not be used here:
|>>>
|>>> $ ./configure -hs
|>>> Configuration of Leafpad 0.8.12:
|>>>
|>>> Optional Features:
|>>> [...]
|>>> --enable-emacs          implement Emacs key theme (experimental)
|>>>
|>>> $ equery uses =leafpad-0.8.12
|>>> [...]
|>>> + + emacs : Adds support for GNU Emacs
|>>>
|>>> As its description says, the flag is intended for GNU Emacs support
|>>> which is not the case here.
|>> i think the USE flag makes sense. perhaps the description should be
|>> changed.
|> Certainly a USE flag makes sense here, but it shouldn't be USE=emacs.
|>
|> The "emacs" global USE flag is used by 82 other packages (all outside
|> the app-emacs category). Its purpose is always that GNU Emacs specific
|> files are installed; either directly, or indirectly by pulling another
|> package via *DEPEND.
|
| why cant it mean both ?  USE flags are intended to control features, not
| dependencies.  often times that just happens to translate into dependencies.
| realistically though, anyone who wants "emacs" wants all emacs "things".  if
| it were to just pull in the emacs dependency, then that could just as easily
| be accomplished by `emerge emacs` and then we can drop the USE flag entirely.
| -mike

If this in an emacs thing, then I guess it includes its own emacs-compatible elisp
implementation with editor primitives exported to the user? Otherwise customizability is
something of a laugh. Keybindings can be rewired. Simply having the same default
keybindings as emacs does not make a package emacsy.

Seeing as this is an editor and a "GTK+ based simple text editor" I doubt it has much
claim to emacs-ness.

If my explanation doesn't make any sense to anyone, please trust our emacs team's
judgement in this.

Marijn

- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkfwhCAACgkQp/VmCx0OL2yXPgCcD2K/7QKMe1V6S2mmXNRj213n
KmkAoJs7Tdrgka4Hgm33AdplqtTf+MH+
=4jAE
-----END PGP SIGNATURE-----
-- 
gentoo-dev@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-31  6:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Jfgrd-0007H6-7k@stork.gentoo.org>
2008-03-30  5:43 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-editors/leafpad: ChangeLog leafpad-0.8.14.ebuild Donnie Berkholz
2008-03-30  6:16   ` Ulrich Mueller
2008-03-30 16:25     ` Mike Frysinger
2008-03-30 17:07       ` Ulrich Mueller
2008-03-30 17:23         ` Mike Frysinger
2008-03-31  6:26           ` Marijn Schouten (hkBst) [this message]
2008-03-31 15:25             ` Mike Frysinger
2008-03-31 16:24               ` Christian Faulhammer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47F08420.70705@gentoo.org \
    --to=hkbst@gentoo.org \
    --cc=compnerd@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox