Jeroen Demeyer wrote:
> On 2015-04-30 08:57, Emmanuel Charpentier wrote:
>> The Developer's guide
>> <http://www.sagemath.org/doc/developer/packaging.html#directory-structure>
>>
>> states the ported packages' tarballs have to be in *lower case* :
>> "The build scripts and associated files are in a subdirectory
>> SAGE_ROOT/build/pkgs/package, where you replace package with a
>> lower-case version of the upstream project name."
> That's about the directory in build/pkgs, not the tarball name.
>
>> 1. What other parts of the build system are broken by mixedCased
>> tarballs ?
> No part of the build system is broken by mixedCased tarball.
>
>> 2. Is this restriction really necessary ?
> There is no such restriction, see answer 1.
Not exactly.
There is (or at least has been) also the convention that the top folder
of a tarball has the same name (case-sensitive) as the tarball (without
.tar{,.gz,.bz2}, and probably also dropping the version, starting with
the first dash). So while there's no problem with mIxEdcAsE package
names, they have to be *consistent* on proper filesystems I think.
We for example recently had trouble with Python, in sage-spkg properly
setting up the source folder for building. (Upstream changed from
lower- to uppercase in the folder name IIRC.)
Not sure how robust sage-spkg meanwhile is.
All folders (package names) in build/pkgs/ are lowercase though; and we
obviously shouldn't have *different* packages "foo" and "Foo" or "FOO", say.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
