Opened 11 years ago
Closed 7 years ago
#39321 closed enhancement (fixed)
Remove old documentation
| Reported by: | marius@… | Owned by: | marius@… |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | base | Version: | 2.1.3 |
| Keywords: | Cc: | neverpanic (Clemens Lang), cooljeanius (Eric Gallager), jmroot (Joshua Root), raimue (Rainer Müller), larryv (Lawrence Velázquez) | |
| Port: | macports |
Description
Remove old documentation from /trunk/doc. It is no longer used and it is just confusing. Also rename doc-new, as it is no longer new.
P.S. I would like to resolve this myself, as a practice task. Just give me the green light.
Change History (10)
comment:1 Changed 11 years ago by cooljeanius (Eric Gallager)
| Cc: | egall@… added |
|---|
comment:3 follow-up: 4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | marius@… removed |
|---|---|
| Keywords: | old doc removed |
| Milestone: | MacPorts Future |
| Type: | update → enhancement |
Related to #39051 which wanted to delete part of that directory.
Note you do not need to Cc yourself when you are the reporter (the reporter is automatically notified), should generally only use keywords from DraftKeywordGuidelines, and that "update" is for port updates (which this is not).
comment:4 follow-up: 5 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to ryandesign@…:
Related to #39051 which wanted to delete part of that directory.
That's different; see comment:ticket:39051:5 for more on how they're different. Also I never wanted to delete it; I just wanted the portfile in it to pass lint. You were the one that wanted to delete it after I brought it up, not me.
comment:6 Changed 11 years ago by larryv (Lawrence Velázquez)
| Cc: | jmr@… raimue@… added |
|---|---|
| Owner: | changed from macports-tickets@… to marius@… |
Replying to marius@…:
So, is it oK to delete the directory ?
It should probably be fine. Cc-ing the rest of portmgr just in case.
If it’s all the same to you, could you move it to my user directory instead of deleting it? Call it “old-doc” or whatever.
comment:7 Changed 11 years ago by jmroot (Joshua Root)
Has anyone gone through and made sure there's nothing in doc that doesn't yet have a counterpart in doc-new?
comment:8 Changed 11 years ago by raimue (Rainer Müller)
The guide is currently generated from trunk/doc-new/. This would need changes to the hosting infrastructure to use trunk/doc/ instead.
comment:10 Changed 7 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
After the move to git, doc-new is called macports-guide and doc is a branch in the same repo called doc-old, so I guess this is fixed.
Cc Me!