Opened 7 years ago
Last modified 5 years ago
#14381 new enhancement
Split m4 spkg from (big) autotools one
| Reported by: | jpflori | Owned by: | tbd |
|---|---|---|---|
| Priority: | minor | Milestone: | sage-6.4 |
| Component: | packages: optional | Keywords: | m4 spkg |
| Cc: | jdmeyer | Merged in: | |
| Authors: | Reviewers: | ||
| Report Upstream: | N/A | Work issues: | |
| Branch: | Commit: | ||
| Dependencies: | Stopgaps: |
Description
Even though we don't make m4 spkg standard yet, I think it's a good idea to split it from the big autotools one.
And as it's a Sage prereq on all platform and it may happen that the usually installed system-wide one can be broken, it will ease things to have it as a separate spkg for people who want to install a recent m4 through m4, or for us if one day we decide to make it standard.
Change History (6)
comment:1 follow-up: ↓ 2 Changed 7 years ago by
comment:2 in reply to: ↑ 1 Changed 7 years ago by
Replying to kcrisman:
This could be helpful on Cygwin?
I don't think so. Note that m4 is a prereq on every platform anyway.
comment:3 Changed 6 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:4 Changed 6 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:5 Changed 6 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:6 Changed 5 years ago by
- Milestone changed from sage-6.3 to sage-6.4
Note: See
TracTickets for help on using
tickets.
This could be helpful on Cygwin?