#52707: trac: Provide search link to port file(s) -----------------------------+---------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Comment (by mkae): Replying to [comment:1 raimue]:

* Trac tickets against specific ports should provide a link to the current Portfile (or ports directory?) Good point, port dir is even better!

* Where would you expect such a link in the ticket UI? It would certainly be best if it was shown in the ticket UI and not (only) in the ticket table.

I imagined all along that the link would be made from the corresponding port field entry, but that has recently been connected to the ticket line already. Bad luck for my proposal, as I am too late... Well, one has to consider as well that the ticket addresses more than one port and thus the user would like to have fast access to all items in that list or ports. So you could just add an additional line to the bottom if the ticket's header below the "Port:" entry called perhaps "Port Directories:" or something along those lines... -- Ticket URL: <https://trac.macports.org/ticket/52707#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X

#52707: trac: Provide search link to port file(s) -----------------------------+---------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Comment (by mkae): Replying to [comment:3 ryandesign]:

What should happen when the Port field contains the name of a subport? Open the portfile which contains the subport.

One could also take into account that the string entered into the port edit field might be a regular expression (e.g. {{{kmymoney4(-devel)}}}) which would require generating more than one link per expression. [Well, I am aware of that this is probably a special case not met that often.] -- Ticket URL: <https://trac.macports.org/ticket/52707#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X

#52707: trac: Provide search link to port file(s) -----------------------------+---------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Comment (by ryandesign): Replying to [comment:4 mkae]:

Replying to [comment:3 ryandesign]:

...

What should happen when the Port field contains the name of a subport? Open the portdir which contains the subport.

What I was trying to point out is that Trac does not currently have that information. It does not know that some ports are subports, and what their portdirs are.

One could also take into account that the string entered into the port edit field might be a regular expression (e.g. {{{kmymoney4(-devel)}}}) which would require generating more than one link per expression. [Well, I am aware of that this is probably a special case not met that often.]

I would consider this a user error, not something we want to support. The Port field should contain port and subport names, not regular expressions. -- Ticket URL: <https://trac.macports.org/ticket/52707#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X

#52707: trac: Provide search link to port file(s) -----------------------------+---------------------- Reporter: mkae | Owner: admin@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+---------------------- Comment (by raimue): Yes, this request will require a new plugin. I was asking what it should look like before we can even start to develop this. However, this will be blocked by getting the PortIndex to DB conversion running on the buildbot first. Using any kind of wildcards, regex, etc. for multiple ports the port field will break he filtering. You will have to list port names only. We could perhaps think about automatic expansion in Trac, but it is usually better to just do that locally with `port echo` to verify your intended result before submitting. -- Ticket URL: <https://trac.macports.org/ticket/52707#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X