References: <b82e8c205ad01b9f6e95b8c482ce192873f2070e.camel@sipsolutions.net>
            <bd4e695d-79ac-249f-5f85-2e8b1832c183@morningstar2.co.uk>
            <0bd9377ae896d7b54baa292a2f7b6e4254f4ec13.camel@sipsolutions.net>
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
            Thunderbird/52.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Message-ID:  <02a034e3-17df-45f2-0fdd-d97cf2678665@morningstar2.co.uk>
Date:         Mon, 27 Aug 2018 08:14:11 +0100
Reply-To:     Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender:       Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From:         Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: \ior_get_str:NN vs. \ior_str_get:NN
To:           LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <0bd9377ae896d7b54baa292a2f7b6e4254f4ec13.camel@sipsolutions.net>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

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