From: Tassilo Horn <tsdh@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: [partially solved]
Date: Tue, 27 Apr 2021 07:33:24 +0200 [thread overview]
Message-ID: <87o8e0p8u4.fsf@gnu.org> (raw)
In-Reply-To: <874kfsvkrq.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
Hi Uwe,
> As I just in my email to Stefan, the auctex version I actually use, is
> compiled from master.
Then the question is how up-to-date that is. If it's maybe around one
month old, it could be the `make-obsolete' calls I've mentioned.
> These other one are some dependencies (I am reminded here on my old
> days on RPM based packages such as SuSe, before switching to Debian).
>
> So how can I resolve this issue?
Well, when you have packages depending on the auctex package, I guess
they'll pull in the auctex ELPA package, no matter if you have the
auctex git checkout on your `load-path' or not. So I'd strongly suggest
you use the auctex ELPA package and not the Git version. I make an ELPA
release from our master after any bug fix anyhow, so it's not that you
would be missing the hot new stuff.
I guess there's also some way to teach package.el that it should assume
some package is already installed in order to stop it from installing
another version due to dependencies but I don't know it from the top of
my head.
Bye,
Tassilo
next prev parent reply other threads:[~2021-04-27 5:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 19:51 Ubuntu 16.04 compiled GNU master, today, various problems, macro-expansion and (void-variable nonascii-insert-offset) Uwe Brauer
2021-04-26 12:05 ` [partially solved] (was: Ubuntu 16.04 compiled GNU master, today, various problems, macro-expansion and (void-variable nonascii-insert-offset)) Uwe Brauer
2021-04-26 12:24 ` Eli Zaretskii
2021-04-26 13:58 ` [partially solved] Stefan Monnier
2021-04-26 14:28 ` Tassilo Horn
2021-04-26 15:31 ` Stefan Monnier
2021-04-26 20:44 ` Uwe Brauer
2021-04-27 5:33 ` Tassilo Horn [this message]
2021-04-27 6:32 ` Uwe Brauer
2021-04-27 7:00 ` Tassilo Horn
2021-04-27 6:43 ` Uwe Brauer
2021-04-27 6:21 ` [Some tests] (was: [partially solved]) Uwe Brauer
2021-04-26 20:41 ` [partially solved] Uwe Brauer
2021-04-27 6:53 ` [shadchen and lsp-mode] (was: [partially solved]) Uwe Brauer
2021-04-27 13:25 ` Ubuntu 16.04 compiled GNU master, today, various problems, macro-expansion and (void-variable nonascii-insert-offset) Stefan Monnier
2021-04-27 20:47 ` Uwe Brauer
2021-04-27 20:50 ` Uwe Brauer
2021-04-27 22:29 ` Stefan Monnier
2021-04-28 13:37 ` Uwe Brauer
2021-05-03 1:49 ` Stefan Monnier
2021-05-03 1:51 ` Stefan Monnier
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=87o8e0p8u4.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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).