Bug#841851: Bug#841852: Bug#841851: ITP: bind-key -- simple way to manage personal keybindings

[Sean Whitton]

Hello Lev,

On Mon, Oct 24, 2016 at 10:38:50PM +0500, Lev Lamberov wrote:
> 24.10.2016 22:27, Sean Whitton пишет:
> > Dear Lev,
> >
> > On Mon, Oct 24, 2016 at 09:55:50AM +0500, Lev Lamberov wrote:
> >> (3) users will rather see their elpa-{bind-key,use-package}
> >> counterparts
> > I don't understand this reasoning.
> 
> I don't get what you don't understand.

There is team convention for source package names, and there is a team
policy for binary package names.  These are completely disconnected: the
team convention for source package names makes no reference to the
binary package name.  So there is no room to argue that the choice of
binary package name should influence the choice of source package name,
except by arguing that the team convention for source package names is
wrong.

Anyway, this is bikeshedding.  There is no need to do another upload.

--
Sean Whitton


signature.asc
Description: PGP signature

Bug#841851: Bug#841852: Bug#841851: ITP: bind-key -- simple way to manage personal keybindings

[Lev Lamberov]

Hi Sean,


24.10.2016 22:27, Sean Whitton пишет:
> Dear Lev,
>
> On Mon, Oct 24, 2016 at 09:55:50AM +0500, Lev Lamberov wrote:
>> (3) users will rather see their elpa-{bind-key,use-package}
>> counterparts
> I don't understand this reasoning.

I don't get what you don't understand.

1. use-package is an upstream project name;
2. bind-key and use-pacakge are package.el package names.

So, in this case:

src:use-package builds bin:elpa-use-package
src:bind-key build bin:elpa-bind-key

What's the question?

Regards,
Lev

Bug#841852: Bug#841851: ITP: bind-key -- simple way to manage personal keybindings

[Sean Whitton]

Dear Lev,

On Mon, Oct 24, 2016 at 09:55:50AM +0500, Lev Lamberov wrote:
> (3) users will rather see their elpa-{bind-key,use-package}
> counterparts

I don't understand this reasoning.

The source package name is based on upstream's project name.  The elpa
package name is based on the package.el package name.

E.g. src:aggressive-indent-mode builds bin:elpa-aggressive-indent (no '-mode').

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#841851: ITP: bind-key -- simple way to manage personal keybindings

[Lev Lamberov]

Hi Adam and Simon,

when it comes to binary packages, their names are elpa-bind-key and
elpa-use-package. Source package names in this case may be misleading, I
agree, but only for those who will see _only_ source package names.
Rationale for these _source_ package names was that (1) these are
upstream names, (2) these are free in Debian, (3) users will rather see
their elpa-{bind-key,use-package} counterparts . Moreover use-package
short description is (as you can see) "use-package declaration for
simplifying your .emacs", which explicitely mentions Emacs.

Cheers!
Lev



signature.asc
Description: OpenPGP digital signature

Bug#841851: ITP: bind-key -- simple way to manage personal keybindings

[Sean Whitton]

Hello,

On Sun, Oct 23, 2016 at 11:28:23PM +0100, Simon McVittie wrote:
> I suggest talking to an Emacs-related packaging team (for example
> Debian Emacs addons team 
> seems to maintain several packages) about whether there is an Emacs
> addon naming convention you can follow.

Team member here.

Note that the binary package will be elpa-bind-key.  So there's not too
much danger of confusion on the part of people looking to install the
package.

Lev, if you weren't aware: for source packages with very generic
upstream names, our convention is to either prepend 'emacs-' or append
'-el' (example source packages in the archive: f-el; emacs-async).

--
Sean Whitton


signature.asc
Description: PGP signature

Bug#841851: ITP: bind-key -- simple way to manage personal keybindings

[Simon McVittie]

On Mon, 24 Oct 2016 at 01:28:27 +0500, Lev Lamberov wrote:
> * Package name: bind-key

This seems like a very generic package name, and gives no indication
that it is to do with Emacs.

I suggest talking to an Emacs-related packaging team (for example
Debian Emacs addons team 
seems to maintain several packages) about whether there is an Emacs
addon naming convention you can follow. From a quick glance at the packages
already in Debian, it might be conventional to disambiguate the purpose
of these packages by calling them something like bind-key-el, or (if obtained
via https://melpa.org/#/bind-key which appears to be an Emacs equivalent of
CPAN) elpa-bind-key.

(Disclaimer: I know nothing about Emacs, other than that it is a highly
extensible text editor. Please talk to someone who knows more than me
before proceeding.)

Bug#841851: ITP: bind-key -- simple way to manage personal keybindings

[Adam Borowski]

On Mon, Oct 24, 2016 at 01:28:27AM +0500, Lev Lamberov wrote:
> * Package name: bind-key
> * URL : https://github.com/jwiegley/use-package
> * License : GPL-2+
>   Programming Lang: Emacs Lisp
>   Description : simple way to manage personal keybindings
> 
> If you have lots of keybindings set in your .emacs file, it can be hard to
> know which ones you haven't set yet, and which may now be overriding some new
> default in a new emacs version. This module aims to solve that problem.

The package's name and short desc look like something I could use... oh
wait, only upon reading the long desc one can see the word "emacs", making
the whole thing as useless as it'd be an extension for vi :þ

Thus, please do warn people about "emacs" more prominently.


Meow!
-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Bug#841851: ITP: bind-key -- simple way to manage personal keybindings

[Lev Lamberov]

Package: wnpp
Severity: wishlist
Owner: Lev Lamberov 

* Package name: bind-key
  Version : 1.0
  Upstream Author : John Wiegley 
* URL : https://github.com/jwiegley/use-package
* License : GPL-2+
  Programming Lang: Emacs Lisp
  Description : simple way to manage personal keybindings

If you have lots of keybindings set in your .emacs file, it can be hard to
know which ones you haven't set yet, and which may now be overriding some new
default in a new emacs version. This module aims to solve that problem.