#19782: Symlink lib64 -> lib
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-7.0
Component: build | Resolution:
Keywords: | Merged in:
Authors: Volker Braun, | Reviewers: Jeroen Demeyer,
Jeroen Demeyer | Volker Braun
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/symlink_lib64_to_lib | 454b14b897e1f2ad1d32d84e8fa5f53c4892d548
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
Replying to [comment:17 jdemeyer]:
> That's standard `configure` stuff, it don't see why it is a
complication.
How many Sage developers are comfortable working with configure.ac? Maybe
5%?
> That's purely a "release management" thing. There is no fundamental
reason for it, it's only because of your workflow.
There is a fundamental reason, OSX doesn't come with autotools so we can't
do the configure.ac -> configure at the client. Any change to configure.ac
necessarily entails further release steps, which is why I really don't
like stuff thats absolutely not configureable in there.
Replying to [comment:18 jdemeyer]:
> It allows for example `sage-env` and other scripts to assume that those
directories exist.
`sage-env` shouldn't do anythning besides setting up the environment, it
certainly shouldn't do anyhing different depending on how far along we are
in the install process.
--
Ticket URL: <http://trac.sagemath.org/ticket/19782#comment:19>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
