Sender: |
|
Date: |
Mon, 27 Aug 2018 08:14:11 +0100 |
Reply-To: |
|
Message-ID: |
|
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
7bit |
In-Reply-To: |
|
Content-Type: |
text/plain; charset=utf-8; format=flowed |
From: |
|
Parts/Attachments: |
|
|
On 27/08/2018 04:08, Benjamin Berg wrote:
> Hey,
>
> On Sun, 2018-08-26 at 09:36 +0100, Joseph Wright wrote:
>> Simply put: update your code.
>
> OK, I get that, and there is only so much you can do obviously.
>
>> We provide a two TL-cycle period for people to update their packages,
>> before removing deprecated commands. The *strong* likelihood is that
>> users updating package X will also update expl3, and vice versa: for
>> most end users, updating is done using their TeX system.
>
> The problem for me is that I am shipping the package separately, which
> means that I am confronted with whatever version the user already has
> on their machine. This obviously completely breaks the above
> assumption, and I fully understand if there is no intention to support
> this corner case better.
I have ask why: CTAN/TL/MiKTeX is pretty smooth.
That said: if a user can install your package, hopefully they can also
install l3kernel/l3packages/l3experimental.
Joseph
|
|
|