Re: [partially solved]

[Uwe Brauer <oub@mat.ucm.es>]

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

>>> "TH" == Tassilo Horn <tsdh@gnu.org> writes:

> 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.

Right, 19th of march, commit 094c29862190290832e60872c2ab1

So I will pull and recompile

>> 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.

Right, only when some testing is going on (like with Al's output
features).
What's about these package that require an older version of auctex?

> 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.

I recall we discussed that somehow in the past (and I did not put the
conclusion in my remember.org file sigh)


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]