John H Palmieri wrote:
> On Thursday, April 30, 2015 at 2:43:43 AM UTC-7, 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
>     
> <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.
> 
> 
> Although anyone who upgrades a package like Pillow may have issues when
> running 'sage-fix-pkg-checksums', because that script assumes that the
> tarball and directory names match exactly (although "Pillow" and
> "pillow" are treated as matching on OS X). Should we modify that script
> to allow mixed case tarballs, but still insist on lowercase directory
> names? That shouldn't be hard to do.

We should certainly fix-sage-fix-pkg-checksums.


There's btw. another inconsistency (IMHO), e.g.:

  ./sage -i Pillow

vs.

  ./sage -i pillow

Which of the above will succeed?  Guess and try yourself... ;-)


(Note that there are (optional) "legacy spkgs" which aren't all
lowercase, so having all lowercase for "new-style" [s]pkg names although
the upstream tarball may be different while for the former slightly
different rules apply is a bit confusing.  Try for example 'sage -i
{TOPCOM,topcom,TopCom}'...)


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

Reply via email to