Opened 6 years ago
Closed 2 years ago
#10110 closed enhancement (fixed)
Developer's Guide: options for packaging
Reported by: | mvngu | Owned by: | mvngu |
---|---|---|---|
Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
Component: | documentation | Keywords: | Developer's Guide, packaging |
Cc: | Merged in: | ||
Authors: | Reviewers: | Karl-Dieter Crisman | |
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
Answer the following often-asked question: What options are available for me to package an existing open source project so that the resulting package can be distributed with Sage? See this thread in the sage-devel mailing list for some materials to use.
Change History (7)
comment:1 Changed 4 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:2 Changed 3 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:3 Changed 3 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:4 Changed 3 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:5 Changed 2 years ago by
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
- Reviewers set to Karl-Dieter Crisman
- Status changed from new to needs_review
comment:6 Changed 2 years ago by
- Status changed from needs_review to positive_review
comment:7 Changed 2 years ago by
- Resolution set to fixed
- Status changed from positive_review to closed
Note: See
TracTickets for help on using
tickets.
This is now pretty well answered at this location, I believe.