minipro: update 0.5

[krischik]

Description

• project moved from github to gitlab
• change maintainer as @ranauei doesn't exist and will break the CI build.
• current version is 0.5
• minipro-query-db command has been removed
• Makefile now supports PREFIX option
• Makefile now supports install with DESTROOT option.

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 10.15.7 19H15
Xcode 12.1 12A7403

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL?
• checked your Portfile with port lint?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?

[macportsbot]

Notifying maintainers:
@ranauei for port minipro.

[macportsbot]

Travis Build #15114 Passed.

Lint results

--->  Verifying Portfile for minipro
--->  0 errors and 0 warnings found.

Port minipro success on xcode10.3. Log
Port minipro success on xcode9.4. Log
Port minipro success on xcode8.3. Log
Port minipro success on xcode7.3. Log

[herbygillot]

Once you feel that things are in a good state, please squash your commits into a single commit, and force-push.

[krischik]

Once you feel that things are in a good state, please squash your commits into a single commit, and force-push.

I don't know how to do that and this is voluntary work there is only that much time I am prepared to spend on your nit picking. Take it or leave it.

[ryandesign]

It's not a problem for us to squash everything into one commit using the GitHub web interface when we merge it.

While I understand that your time is limited, you should be prepared for others to review the work you submit. We are all trying to work together to help MacPorts continue to be a consistent high-quality product.

[ryandesign]

You're right, GitHub handle @ranauei doesn't exist today. I feel fairly certain that it did exist when I added it to the ports this person maintains in #1796.

Did you contact this person by email to discover if they have a new GitHub handle or if they still wish to maintain this port?

This person maintains other ports. The maintainers line of all the ports should be fixed simultaneously.

[ryandesign]

I've now filed a port abandonment ticket for this.

[kencu]

Here is why I didn't:

I first saw this was a ticket submission from 6 years ago, committed by Kurt. The submitted version was 0.0.1.

We have never seen or heard from the supposed maintainer since, in five years.

All the changes in the port since being committed initially were mostly done by you and larry.

The supposed maintainer has no other ports.

So -- IMHO -- this did not need a port abandonment ticket, as it was clearly either abandoned at birth or immediately post-partum.

[ryandesign]

As I said above:

This person maintains other ports. The maintainers line of all the ports should be fixed simultaneously.

[kencu]

that is fair.

[ryandesign]

Just as the github portgroup helps simplify ports hosted at github, the gitlab portgroup should be used to simplify ports hosted using gitlab.