Opened 11 years ago
Closed 11 years ago
#39191 closed submission (fixed)
Submission: tinc-devel @1.1pre7
| Reported by: | mike@… | Owned by: | larryv (Lawrence Velázquez) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | tinc-devel |
Description
tinc has a 1.1pre7 (pre-release) branch, which adds many enhancements.
1.0.21 is still the stable version.
Attachments (1)
Change History (6)
Changed 11 years ago by mike@…
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
| Cc: | mike@… added |
|---|---|
| Version: | 2.1.3 |
Maybe this could be called “tinc-devel”?
comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)
| Cc: | mike@… removed |
|---|
Oops, you’re the reporter.
Is there any particular reason to specify the version in the port name?
comment:3 follow-up: 4 Changed 11 years ago by mike@…
The only reason the version is in the port name is because package 'tinc' already exists.
We could call this tinc-devel if you prefer.
comment:4 Changed 11 years ago by larryv (Lawrence Velázquez)
| Owner: | changed from macports-tickets@… to larryv@… |
|---|---|
| Port: | tinc-devel added; tinc-1.1 removed |
| Status: | new → assigned |
| Summary: | tinc-1.1 @1.1pre7 pre-release version → Submission: tinc-devel @1.1pre7 |
Replying to mike@…:
The only reason the version is in the port name is because package 'tinc' already exists.
We only put the version into the port name if the version is important for dependents (e.g., if a library’s API is tied to particular releases). If this port is just intended to represent tinc’s unstable branch, then we should probably go with “tinc-devel”.
comment:5 Changed 11 years ago by larryv (Lawrence Velázquez)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Since the portfile is almost identical to tinc’s, I just made tinc-devel a subport. r106334.
Portfile