Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id s7VJxpdP002771 for ; Sun, 31 Aug 2014 21:59:52 +0200 Received: from relay2.uni-heidelberg.de ([129.206.210.211]) by mx-ha.gmx.net (mxgmx007) with ESMTPS (Nemesis) id 0M3N2W-1YF2vJ1M5w-00qxMj for ; Sun, 31 Aug 2014 21:59:45 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s7VJvaq3032406 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 31 Aug 2014 21:57:36 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s7VCDtBC025571; Sun, 31 Aug 2014 21:57:36 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 11292874 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 31 Aug 2014 21:57:36 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s7VJvawr002928 for ; Sun, 31 Aug 2014 21:57:36 +0200 Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id s7VJvSNt012338 for ; Sun, 31 Aug 2014 21:57:31 +0200 Received: from mittelbach-online.de (pD9FE3653.dip0.t-ipconnect.de [217.254.54.83]) by mrelayeu.kundenserver.de (node=mreue104) with ESMTP (Nemesis) id 0M0ACi-1YIKk01SI8-00uKnt; Sun, 31 Aug 2014 21:57:28 +0200 Received: from [192.168.123.104] (falco [192.168.123.104]) (Authenticated sender: frank) by mittelbach-online.de (Postfix) with ESMTPSA id A10C9285392 for ; Sun, 31 Aug 2014 21:56:55 +0200 (CEST) User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 References: <54033B96.8070007@morningstar2.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-ID: A10C9285392.A068A X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details X-MailScanner-From: frank.mittelbach@latex-project.org X-Spam-Status: No X-Provags-ID: V02:K0:522Glf4rD521pjxum3W6yGZ43qH+tYi0r9qxqwytmFw YWvjTbdplIhpeRQQvqMlg3ss2Zq3YKJkeL8EE2LY/HBrIrdVkV esFQuhK30d1dud/DA34SfNI3buhhbzM+23JoWzKs88X0SbWKyk ixCdIbk1N6IUo7vZDsoWNOvk4QLPBFe6XF/B6IYMK80jScmtOw TFGWZ2yTA+y0WQHwZUl1hSKyAf1cqlyUZnU20TN3BQq+i+LTpg P5+x1W+Bv9+h4Q38qMZXNa5Z4pmLYpVcy25OtEq1P6e/qGxk7x tsuMRhdK/U/N6LYi7O8RQ70+vs2QSbBKCXJn5LxmZKeWPF3KxY mKMrfW0FGa3RwybNFAEAWCLo//WqxZeGKPUyMJs1ZhO0Fa4nrg o2Q5F3KGgy8KQ== Message-ID: <54037E00.9050005@latex-project.org> Date: Sun, 31 Aug 2014 21:56:48 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: How to get l3str.sty, l3seq.sty, etc. these days? To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: Envelope-To: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=V3; X-GMX-Antivirus: 0 (no virus found) X-UI-Filterresults: notjunk:1;V01:K0:1uzYQMHVRDw=:dwfSKp/bpK0KH8pwR9j9fJnYjf FF2kJPs9oTHOUmqoGHOD41ziupeAsk6vkjf0gnmvlbqp6BTFMHvpnIYn5eo6nVt8wmZ4mx2A/ twei6QkRoezrKI4yNLyG8JWjOMU6d0SZNYD2+L+5ZA9DkVO5AKjoZ9sjn5QTxvFgRUdPR5743 YPFgg9EMbSaQ20PynscE/JxA2pshlxSt2061vRvRXhv0c9Jo0E2ARSxdNDGcWENJYDMW5wFaQ iZkzEtACrjAaeXAw7/DC8vqGsx+4xrcKLLOGQu+L3THOcCQJc5TqK6UrhZHK9urRn/5P6t2fO 6Q3l1zEpSjw8aIKfYEqoXSdQsMSWV1cmd2Zj9VjQMFM9bgQg17SEmMBfL2u2I1Q0/pGfaBcl4 7hoVIsZR+P9ofB8fYyJSo+IEa0khQaNXkMmQSjMloyE5zR/FgOtp/qlyd2fN0q6h38OatxcC0 04AayUFM/u7EQoefFMefiCF2GhXSyaN+1wKf/8jalgJijP3t8fyIEjnrF/V8Zffd1jGE/YnvX 4xDtIccpH4yuY2x/8slShzHs2OtoQ6NZIW5rsoOy/2cufw16U75dfPa6plPEkUXMmqbjaVKdJ bN9oUpm1FwVVstB4mrtX5x5aWRblABT17+RR31rq+njcQZ5muet4elDMQn/erkxPuZZKV2IYO 4gKc8BzGgQSTYqm22JGxkW+VrSCikxGSJ4XRd6vSC/nOMMXRCr0fq2XM5mu6Vx6djDhhHdNbE yzD4RsHsMTg46JpPqzHl1O+jMSsBxNnRaFZMAUAfHgjYJV2sFpBtkWAImhvh8Mv+MagcjsP11 h4OJoC/2YgTdFg/zJpbd2vt55sXY/t1n1rQgplr12/vfBygziVNBwO1DP3gsk9zPVDGzvJv+p EpKHV83WsEuRsMP4kqe6TqUUT5l51gYpAuZLHhIxUE8/4e5PzitYGt5r9p7SLsq0EFmLAyH95 9lzaAwMsvjKmy/o6B7sJN8NHg4PUGwFuKqq4+lyfswTW+iQj5U6OfBxJ6ELtAGSc8eGoF+nx1 K/s0n0CkCuRZqCSdkUNaAythWfOuF3f0ljMGR2FnwfJzbfcca0SHEmlM3UMH6L5usuX56WHJT YWE9idECjCC/1OOPRbkXvYrw+Iyechoi/kmvI39DiVDTyh1IEq8/SuyKnaJ/AmVMsfmYmVRAH RFNK8r6raHyzk/M9GQJ+0z+5gDbZrSeYRzhHZw+JThR3rjUW+LWoS5GZSQsw8QNTccI6O/7lj HV/fQtm32LYJsU1ENg0ZD4pANNt3NyZQ36+byVMTGV22F/IVhtoYV9QhNT6Ux76+0pLwR8bg0 cMavPNvsBwTgBjey8smEN2LYTzGWLCkkfKRSujZWt87rtlITtsVnlATNmiW2ehcoF76gnMnl1 /+iEOb8GWf9lEi9kpsF8kuBGEa9+0BsVctk4D00EXo3/b2XrbzHuZyI7Xg4ETAW7IPP3WqjxS b3X1U4pEi873ZmQ/Q50PQib6jAg2iu6zNAJrbn7RZOABRUlnZOHxmDb8UsLvJVwTZmHhj69g= = X-UI-Loop:V01:BXh5Q9JhGgw=:2AaiwxsfZ65SNg3sohul5vNq9GXoNMh0MHn9PAifHAA= X-UI-Out-Filterresults: notjunk:1; Status: R X-Status: X-Keywords: X-UID: 7584 Hi Michiel > Let me put it like this. Until now, I've always been able to do this: > > \RequirePackage{expl3} > \RequirePackage{l3prop} > > But now, this gives me the error message: > > ! LaTeX Error: File `l3prop.sty' not found. correct. This is because we finally removed the individual .sty files. Initially, during the first phases of expl3 (when new datatypes got added and a lot got changed or updated within those datatypes) it was useful to have those as individual module files that could be loaded individually (and replaced for testing etc) but once things stabilized this became a problem as people loaded them in wrong order etc and we had to try to maintain all kind of dependency rules between the different files so that in the end normally most if not all of expl3 got loaded anyway. Therefore we announced way back that one should always load expl3 and not any individual files. and now we finally extract everything into a single file and the individual files only exist on the source level (just like LaTeX2e where you have many source files (.dtx) but only a single latex.ltx So I guess you have to bite the bullet and remove the calls to individual files as it really don't make any sense to provide empty .sty files just to support the above scenario regards frank