Changes between Version 17 and Version 18 of Ticket #29500
- Timestamp:
- Sep 8, 2020, 5:33:10 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #29500
-
Property
Status
changed from
new
toneeds_review
- Property Cc jhpalmieri added
-
Property
Authors
changed from
to
Matthias Koeppe
-
Property
Status
changed from
-
Ticket #29500 – Description
v17 v18 7 7 2. Then install the wheel. 8 8 9 The wheels in `$SAGE_SPKG_WHEELS` persist after the completed build. We manage them using the DESTDIR staging mechanism -- there will be exactly 1 wheel for each installed package.9 The wheels in `$SAGE_SPKG_WHEELS` persist after the completed build. We manage them using the `DESTDIR` staging mechanism -- there will be exactly 1 wheel for each installed package (and removing a package removes the wheel). 10 10 11 11 Users can create virtual environments and install the wheels built by the Sage distribution into them, using standard tools such as `pip install --find-links`. 12 12 13 In this ticket, we keep using the DESTDIR staging mechanism also for the installation of the package from the wheel. This can be changed later -- to remove the problems described in #29585 -- by just holding the pip lock (if it is at all still necessary after the major pip upgrades in the 9.2 series) during the wheel installation (step 2). 13 - In follow-up ticket #30527, we create a PEP 503 simple repository for the wheels built during installation, which enables more convenient installation options for users. 14 14 15 Follow-up: #30527 Create PEP 503 simple repository for wheels built during installation 15 16 In this ticket, we keep using the `DESTDIR` staging mechanism also for the installation of the package from the wheel. 17 18 - In a follow-up ticket, we can change this -- to remove the problems described in #29585 -- by just holding the pip lock (if it is at all still necessary after the major pip upgrades in the 9.2 series) during the wheel installation (step 2). 16 19 17 20 -------