Emacs packaging guidelines

Michael Schwendt mschwendt at gmail.com
Thu Jul 30 11:22:37 UTC 2015

On Thu, 30 Jul 2015 12:02:05 +0100, Jonathan Underwood wrote:

> On 30 July 2015 at 11:48, Vít Ondruch  wrote:
> [snip]
> > These are definitely fair points, but at the end, this should be left up
> > to the maintainer if there will be -emacs package and the general
> > preference should be to support the subpackages. I hope it will give as
> > greater opportunities with incoming boolean dependencies, such as
> > "install the -emacs subpackage when emacs is already installed".
> >
> Perhaps so - I encourage you to prepare a new draft of the guidelines
> to encapsulate how you'd like to see this work for the FPC to
> consider. I'll happily read over anything you write, if you like, and
> help where I can.

The beauty of %{parent}-%{child} naming is that it is your only hope if you
want to browse what's available for Emacs,

  dnf list emacs\* | less

or a similar search in other package tools. Especially if there are
hundreds or thousands of packages in that list. Else you need to know
exactly what to search for ==> a very limited target group (people pick
a very few packages and won't ever care about the other thousands ones,
since it's not feasible to become familiar with what's available).

  $ dnf list \*-fonts|wc -l

*sigh*  Searching for "font" gives a few hundred more results.

My stomach ;) would prefer reducing the number of packages in a namespace
to a dozen or at most 20 large ones to get "everything" in less pieces,
but when building from individual src.rpm packages, that would require
a completely different build-/packaging-system.

Off-topic, oh well. :-)

More information about the devel mailing list