[MacPorts] #18632: Finding perl ports that are part of other ports is too hard
#18632: Finding perl ports that are part of other ports is too hard ------------------------------+--------------------------------------------- Reporter: scott@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 1.7.0 Keywords: | Port: ------------------------------+--------------------------------------------- I love MacPorts, it makes my life easier, sometimes, it makes my life harder. What is the solution to solve this? Example Case: port search p5-Tie-RDBM No match for p5-Tie-RDBM found Search MacPorts http://www.macports.org/ports.php?by=name&substr=rdbm Nothing Search CPAN http://search.cpan.org/~lds/Tie-DBI-1.02/lib/Tie/RDBM.pm Finds it with no issue Now I am stuck, do I make a port for it? I did, I think I wasted my time. port search p5-Tie-DBI p5-tie-dbi @1.02 (perl) Nie:DBI This distribution contains Tie::DBI and Tie::RDBM I do not really know what to suggest, I brought it up on the mail list a while back. There was opposition to adding more data to the portfile, opposition to my suggestion to add another field for the purpose of listing ports that contain other ports. At this point, I would at least suggest, that in cases like this, some "stub" record be added to the web based port search. Ideally, it should all be handled in the ports on the command line. CPAN makes me want to barf, almost all the time, CPAN wins in this case, as it finds what I need, on the web, or in the command line. -- Ticket URL: <http://trac.macports.org/ticket/18632> MacPorts <http://www.macports.org/> Ports system for Mac OS
#18632: Finding perl ports that are part of other ports is too hard ------------------------------+--------------------------------------------- Reporter: scott@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.0 Keywords: | Port: ------------------------------+--------------------------------------------- Changes (by jmr@…): * milestone: MacPorts Future => -- Ticket URL: <http://trac.macports.org/ticket/18632#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#18632: Finding perl ports that are part of other ports is too hard ----------------------+-------------------------------- Reporter: scott@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.0 Resolution: | Keywords: Port: | ----------------------+-------------------------------- Description changed by ryandesign@…: Old description:
I love MacPorts, it makes my life easier, sometimes, it makes my life harder. What is the solution to solve this?
Example Case: port search p5-Tie-RDBM No match for p5-Tie-RDBM found
Search MacPorts http://www.macports.org/ports.php?by=name&substr=rdbm Nothing
Search CPAN http://search.cpan.org/~lds/Tie-DBI-1.02/lib/Tie/RDBM.pm Finds it with no issue
Now I am stuck, do I make a port for it? I did, I think I wasted my time.
port search p5-Tie-DBI p5-tie-dbi @1.02 (perl) Nie:DBI This distribution contains Tie::DBI and Tie::RDBM
I do not really know what to suggest, I brought it up on the mail list a while back. There was opposition to adding more data to the portfile, opposition to my suggestion to add another field for the purpose of listing ports that contain other ports.
At this point, I would at least suggest, that in cases like this, some "stub" record be added to the web based port search. Ideally, it should all be handled in the ports on the command line.
CPAN makes me want to barf, almost all the time, CPAN wins in this case, as it finds what I need, on the web, or in the command line.
New description: I love MacPorts, it makes my life easier, sometimes, it makes my life harder. What is the solution to solve this? Example Case: {{{ port search p5-Tie-RDBM No match for p5-Tie-RDBM found }}} Search MacPorts [[br]] http://www.macports.org/ports.php?by=name&substr=rdbm [[br]] Nothing Search CPAN [[br]] http://search.cpan.org/~lds/Tie-DBI-1.02/lib/Tie/RDBM.pm [[br]] Finds it with no issue Now I am stuck, do I make a port for it? I did, I think I wasted my time. {{{ port search p5-Tie-DBI p5-tie-dbi @1.02 (perl) Nie:DBI This distribution contains Tie::DBI and Tie::RDBM }}} I do not really know what to suggest, I brought it up on the mail list a while back. There was opposition to adding more data to the portfile, opposition to my suggestion to add another field for the purpose of listing ports that contain other ports. At this point, I would at least suggest, that in cases like this, some "stub" record be added to the web based port search. Ideally, it should all be handled in the ports on the command line. CPAN makes me want to barf, almost all the time, CPAN wins in this case, as it finds what I need, on the web, or in the command line. -- -- Ticket URL: <https://trac.macports.org/ticket/18632#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#18632: Finding perl ports that are part of other ports is too hard ----------------------+-------------------------------- Reporter: scott@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.7.0 Resolution: invalid | Keywords: Port: | ----------------------+-------------------------------- Changes (by macsforever2000@…): * status: new => closed * resolution: => invalid Comment: I'm not sure what we are supposed to do here. Your search was too specific. Searching for "RDBM" finds the port you were looking for. -- Ticket URL: <https://trac.macports.org/ticket/18632#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts