-
-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sage.env: Remove direct uses of SAGE_LOCAL from the Sage library #32036
Comments
comment:1
There are a few remaining uses of |
comment:2
(see #30819 |
comment:3
Perhaps now is also the time that we do #30914 (Meta-ticket: Create upstream repositories, pip-installable packages for database packages)? |
comment:4
Replying to @mkoeppe:
That would be timely if we could. Other issue about |
comment:5
No, |
comment:6
Replying to @kiwifb:
Scratch that, I think I did myself in at build time for some reasons (which I have top check). |
Commit: |
New commits:
|
Author: Matthias Koeppe |
comment:9
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:11
Thanks for catching this! |
comment:12
Next issue:
and, after bypassing it
|
comment:13
Excluding
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:16
Perhaps someone who knows more about GAP workspaces can comment whether this change makes sense. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:18
Replying to @kiwifb:
I agree. Could someone on such a distro take care of lie.py please? There's no package for homebrew and our SPKG does not compile |
comment:69
Replying to @dimpase:
Using layman is so outdated - even I moved on (last month :) ). Seriously, it is deprecated.
or |
Reviewer: Dima Pasechnik |
comment:70
OK |
comment:71
Thanks! |
comment:72
On OSX:
|
comment:74
I see, we forgot to replace |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:76
Yes, looks like I fell asleep in the middle of rewriting this function. |
comment:77
Replying to @mkoeppe:
The new code should do the trick. I must say that when we were working on this originally, it felt like you were in my time zone. So, I guess falling asleep would have been fair. |
Changed reviewer from Dima Pasechnik to Dima Pasechnik, François Bissey |
comment:78
Thanks! |
comment:79
I must say, this is not as useful without setting
in a good number of doctests. This wouldn't happen with As an aside, I tried to fix it by adding a line |
comment:80
Didn't we take care of this in #32057? |
comment:81
Replying to @mkoeppe:
#32057 helps with build time but not runtime - as it should, |
comment:82
Right, thanks. So, as discussed in #31338 comment:18, we're back to having to solve the same problem as #31578. |
comment:83
That complaint of mine was about build time. We had the runtime issue forever, it is just the opportunity to squash it is gone again :( But what I want to know and I'll dig is why setting |
comment:84
I think I will just adopt the commit you removed for Antonio. |
comment:85
Replying to @kiwifb:
Interestingly, adopting it broke docbuilding. So, there is probably more work to do on that subject in a follow up ticket. |
Changed branch from u/mkoeppe/sage_local_extinction_path to |
(from #31338 comment:13)
These changes are preparation for modularization and is also intended to make downstream packaging easier.
CC: @kiwifb @antonio-rojas @dimpase @videlec @jhpalmieri
Component: build: configure
Author: Matthias Koeppe, François Bissey
Branch/Commit:
985af6e
Reviewer: Dima Pasechnik, François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/32036
The text was updated successfully, but these errors were encountered: