It seems that a consensus on those issues should be reached *before* patching anything : the different behaviors of different platforms (Macs nvs other Unices, and do not forget Windows, which is still a target...) make some assumptions hardly enforceable (or even checkable). The scripts should *not* rely on them.
HTH, -- Emmanuel Charpentier Le jeudi 30 avril 2015 08:57:57 UTC+2, Emmanuel Charpentier a écrit : > > 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." > > I am wondering what parts of the build system needs this restriction, that > seems to be unenforceable on Macs (see trac#18229 > <http://trac.sagemath.org/ticket/18229> for discussion, and examples in > trac#16759 <http://trac.sagemath.org/ticket/16759> and trac#18341 > <http://trac.sagemath.org/ticket/18341>), and possibly on Windows, if and > when we have a Windows native version. The sage-fix-pkg-checksums script, > which creates packages checksums, is known not to treat mixedCased > tarballs. So, two questions : > > 1. What other parts of the build system are broken by mixedCased > tarballs ? > 2. Is this restriction really necessary ? > > HTH, > -- > Emmanuel Charpentier > > -- 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.
