unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] Re: etags name collision.
Date: Tue, 12 Apr 2022 13:13:02 +0200	[thread overview]
Message-ID: <20220412111302.ore2hikj4yxftuxz@Ergus> (raw)
In-Reply-To: <u1qy2yjtw@gentoo.org>

On Tue, Apr 12, 2022 at 07:03:23AM +0200, Ulrich Mueller wrote:
>>>>>> On Tue, 12 Apr 2022, Eli Zaretskii wrote:
>
>>> Date: Mon, 11 Apr 2022 21:53:50 +0200
>>> From: Ergus <spacibba@aol.com>
>>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>>>
>>> >I still think that any test for an installed binary is a bad idea, from
>>> >a distro point of view. Note that distros typically build packages in an
>>> >environment that is different from the one of the final target system.
>>> >
>>> Here I agree
>
>> How else to test whether this is needed?  I'm okay with having
>> "--without-ctags" with no test, but then the default will have to be
>> to install our ctags.
>
>That sounds good.
>
>> With the test, we could refrain from installing it if the test says
>> so.
>
>But then the test should be more specific, and check if there would be a
>file collision at the actual target location (with the name modified by
>--program-transform-name, if applicable). If there's no collision (e.g.
>Emacs ctags has a different name) then Emacs should install it.
>
If we don't do that with mailutils why should we do it with ctags... It
will be more complex and error prone. I would be even simpler and just
add the option --without-ctags to not build our ctags on demand
unconditionally, keeping things as they are now by default.

as a plus we could make: --with-ctags=no, to not build; and we could
allow to do things like: --with-ctags=ctags.emacs to explicitly create
it as ctags.emacs... But I am sure such method will break some standard
or development agreement.


>> I'm also okay with leaving things as they are now, obviously, if this
>> change brings more problems than it solves.  I don't consider the
>> current situation bad enough to necessitate any changes.
>
>Things are like this since more than a decade, and obviously distros can
>cope with the status quo.

1) Then exuberant ctags was not so popular
2) The popular languages then were very different than today (even C++
was very different then)
3) There was not universal ctags which supports all of them and our formats.



  reply	other threads:[~2022-04-12 11:13 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220411124736.3qijvtearh6wlen7.ref@Ergus>
2022-04-11 12:47 ` etags name collision Ergus
2022-04-11 13:18   ` Eli Zaretskii
2022-04-11 13:38     ` Dmitry Gutov
2022-04-11 13:52       ` Ergus
2022-04-11 14:11         ` Eli Zaretskii
2022-04-11 14:25           ` Ergus
2022-04-12  7:16             ` Alfred M. Szmidt
2022-04-12  8:30               ` Andreas Schwab
2022-04-12 10:48               ` Ergus
2022-04-12 10:51                 ` Po Lu
2022-04-12 11:03                   ` Ergus
2022-04-12 11:13                   ` Dmitry Gutov
2022-04-12 11:28                     ` Po Lu
2022-04-12 13:45                       ` Alfred M. Szmidt
2022-04-12 14:29                         ` Dmitry Gutov
2022-04-12 15:36                           ` Óscar Fuentes
2022-04-12 17:13                           ` Ergus
2022-04-12 13:45                   ` Alfred M. Szmidt
2022-04-12 13:45                 ` Alfred M. Szmidt
2022-04-12 16:40                   ` Ergus
2022-04-12 17:21                     ` Alfred M. Szmidt
2022-04-12 17:48                       ` Ergus
2022-04-12 19:50                         ` Alfred M. Szmidt
2022-04-12 20:49                           ` Dmitry Gutov
2022-04-13  5:45                             ` Alfred M. Szmidt
2022-04-12 17:53                       ` Stefan Monnier
2022-04-11 13:59       ` Andreas Schwab
2022-04-11 14:07       ` Eli Zaretskii
2022-04-11 13:47     ` Ergus
2022-04-11 14:09       ` Eli Zaretskii
2022-04-11 14:18         ` Ergus
2022-04-11 15:46         ` [PATCH] " Ergus
2022-04-11 15:51           ` Eli Zaretskii
2022-04-11 16:19             ` Ergus
2022-04-11 16:40               ` Eli Zaretskii
2022-04-11 19:19                 ` Ergus
2022-04-11 19:39                   ` Ulrich Mueller
2022-04-11 19:53                     ` Ergus
2022-04-11 21:04                       ` Ulrich Mueller
2022-04-11 22:20                         ` Ergus
2022-04-12  7:21                           ` Alfred M. Szmidt
2022-04-12  7:34                             ` Ulrich Mueller
2022-04-12 10:53                             ` Ergus
2022-04-12  2:28                       ` Eli Zaretskii
2022-04-12  2:43                         ` Po Lu
2022-04-12  5:03                         ` Ulrich Mueller
2022-04-12 11:13                           ` Ergus [this message]
2022-04-12 11:48                             ` Eli Zaretskii
2022-04-12 11:56                               ` Eli Zaretskii
2022-04-12 12:50                             ` Ulrich Mueller
2022-04-12  7:16                         ` Alfred M. Szmidt
2022-04-12 12:15                   ` Eli Zaretskii
2022-04-11 16:46         ` Stefan Monnier
2022-04-11 17:01           ` Eli Zaretskii
2022-04-11 17:41             ` Stefan Monnier
2022-04-11 18:15               ` Eli Zaretskii
2022-04-11 19:11                 ` Ulrich Mueller
2022-04-12  7:42                 ` Thierry Volpiatto
2022-04-11 18:15               ` Ergus
2022-04-11 23:09               ` Ergus
2022-04-11 14:10     ` Andreas Schwab
2022-04-11 13:56   ` Kaushal Modi
2022-04-11 14:16     ` Óscar Fuentes
2022-04-12  3:19   ` Richard Stallman
2022-04-12  7:16     ` Alfred M. Szmidt

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20220412111302.ore2hikj4yxftuxz@Ergus \
    --to=spacibba@aol.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ulm@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.
Code repositories for project(s) associated with this public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).