all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Tim Gesthuizen <tim.gesthuizen@yahoo.de>,
	Pierre Neidhardt <mail@ambrevar.xyz>
Cc: 33359@debbugs.gnu.org
Subject: bug#33359: On emacs-clang-format
Date: Wed, 14 Nov 2018 11:25:13 +0100	[thread overview]
Message-ID: <87o9asj6ra.fsf@gnu.org> (raw)
In-Reply-To: <dbdd6fc0-e6c7-6f7a-f140-c742bcdf2734@yahoo.de> (Tim Gesthuizen's message of "Mon, 12 Nov 2018 22:40:13 +0100")

Hi Tim,

Thanks for your feedback.

Tim Gesthuizen <tim.gesthuizen@yahoo.de> skribis:

> I noticed that someone packaged emacs-clang-format.
> There are some problems with the current package definition:
>
> - clang already distributes the same functionality (Maybe I am missing a
>   feature that clangs version does not have though).
> - The package also includes integration for clang-rename.
> - The package should probably have a more generic name and function as a
>   package for all emacs integration clang offers.
> - The clang package is installing the same files under share/clang.
>   Maybe those should be removed.
> - The license is incorrect. The version that is cloned from github
>   also seems to have some licensing issues (Missing full license...)
>
> You'll find an example package definition attached.
> This can probably be optimized a little bit more so that the full clang
> tarball does not need to be extracted twice.

Pierre, WDYT?

Thanks in advance!  :-)

Ludo’.

  reply	other threads:[~2018-11-14 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12 21:40 bug#33359: On emacs-clang-format Tim Gesthuizen
2018-11-14 10:25 ` Ludovic Courtès [this message]
2018-11-14 10:48   ` Pierre Neidhardt
2018-11-14 15:56     ` Tim Gesthuizen
2018-11-26 13:54       ` Pierre Neidhardt

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=87o9asj6ra.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33359@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    --cc=tim.gesthuizen@yahoo.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.