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

2016-10-24 Thread 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

2016-10-24 Thread 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