-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
py-dns, lamson: delete ports #3316
Conversation
Travis Build #4749 Passed. |
Does anything depend on either of these two? If not, I think we can probably get rid of them, yes. |
It appears so for py-dns:
|
The fact that there are dependent ports seems like an issue. |
@mf2k I appreciate you checking, I had not used that command, nor was I expecting it to list that many ports after searching portfiles for However, since
I'm not sure if this is the expected or documented behavior, since the guide has the usage:
rather than some sort of |
Regex works, do: Looks safe to remove both. |
Interesting, I did not realize that. Thank you both! |
Actually, it looks like that'll only match if py27-dns is the last dependency (it is, in this case). So something more like:
Would be better if we supported more regex, something like this:
Still, in this case it looks like lamson and py-dns are alone and ok to remove. |
Okay, so is it agreed that it's safe to remove both? If so, I'll commit the change soon. |
@pmetzger: Yes, it is safe to remove them. |
Merged. Thanks, @chrstphrchvz! |
Best way is probably |
@jmroot This is a sufficiently frequently wanted feature (checking if something depends on precisely a particular other port, with nothing else accepted) that perhaps we should have our own way of specifying that in the command without needing a regex anchor. |
Description
Lamson's repository was last updated ~2013, and its homepage was already offline in 2015. There is an actively maintained GPLv3 fork of it, Salmon, which doesn't already have a port. There is a 5-year-old open ticket for this port (missing dependency not in MP): https://trac.macports.org/ticket/40001
PyDNS does not appear to be maintained by its developer any longer. It was last updated in 2012 (2.3.6, which MP never adopted), and it does not support Python 3. dnspython seems like the far more popular and actively maintained alternative; but since it's not a drop-in replacement for PyDNS, and the only dependent of
py-dns
islamson
, I think the port can be removed.I'm not familiar with deleting ports, so any advice or suggestions are appreciated. I'd be interested in cleaning out more old ports, yet I imagine it might be either more worthwhile or a higher priority to focus on more actively-used/maintained ports.
Also, should Python packages that happen to be named "PyFoo" have their ports consistently named
py-pyfoo
instead ofpy-foo
? I think doing so is better at preserving/respecting the package's name, and also so that thepy-
prefix only indicates it's a Python-related port and avoids confusion of whether the package itself is named "Foo" or "PyFoo". I can ask on the dev mailing list unless there's already a consensus. I haven't yet found any examples which are actively maintained though.