Opened 14 years ago
Closed 7 years ago
#25984 closed defect (wontfix)
asterisknow needs to use a specific version of the software
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | stefan.van.der.eijk@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.1 |
| Keywords: | Cc: | sewebster@… | |
| Port: | asterisknow |
Description
asterisknow fetches from the 2.0 branch in asterisknow's svn. This is not acceptable as it means different users installing at different times will receive different versions of the software as upstream commits changes to the 2.0 branch. The port must instead pull a specific version of the upstream software, for example from a specific tag, preferably also pegged with a revision number.
I see a 2.0.4 tag exists, so the port should presumably be updated to version 2.0.4.
Change History (4)
comment:1 follow-up: 3 Changed 14 years ago by sewebster@…
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to sewebster@…:
So if I want to patch my portfile to grab 2.0.4 can I just change the version line to 2.0.4 and the existing "fetch.type svn" option will grab that tag for me?
No; you must additionally instruct subversion how to fetch that version, for example by modifying svn.url to be the URL to the appropriate tag, and/or by setting svn.revision to be the revision of the repository to fetch.
comment:4 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
So if I want to patch my portfile to grab 2.0.4 can I just change the version line to 2.0.4 and the existing "fetch.type svn" option will grab that tag for me?