RENAME/UPDATE: Git 1.5.2

[zacheryph@…]

This renames git to its rightful name (git-core -> git) as its no longer called git-core and is a product in its own right.

• delete_git-core.patch: removed devel/git-core
• add_git.patch: adds devel/git with proper updates from git-core to handle new package version
• update_cogito.patch: update cogito to depend on git instead of git-core.

currently the docs does not work as xslt parcer tries pulling a file from sf.net, im hoping this might be temprary, if anyone knows so, or a way to fix it please tell me.

[zacheryph@…]

removed devel/git-core

[zacheryph@…]

updates cogito to depend on git not git-core

[zacheryph@…]

This patch shows me as maintainer, though should prolly say bryan and me. other notes:

• this nullifies Ticket #11962 and can be closed will not fix. i added a comment on there as well.
• i removed NO_DARWIN_PORTS from args list as i didn't see a reason for being there, and runs perfectly fine with it removed.

[bryan@…]

Certainly git is probably a better name than git-core (which was the right name in 2005 when I first created the Portfile), but there are lots of users of this port, most of whom won't get the upgrade if we change the name. So, IMHO, the name change does more harm than good. It's not a surprising name, it's what the Linux distributions use.

FYI, NO_DARWIN_PORTS is technically correct. At one time it was required, but now it isn't. NO_DARWIN_PORTS means don't add the flags necessary to use the MacPorts libraries. The port system has already added these flags, so doing it twice is (potentially, but not in this case) problematic.

[zacheryph@…]

fix man page install, remove old dependancies

[boeyms@…]

I've committed patch-11962-7333 from #11962 in r25898, which contains the version bump.

Since the list of maintainers for the git-core port does not contain the openmaintainer@... address, the people who maintain the port and how it is maintained is at the discretion of the currently listed maintainer(s) (in this case Bryan).

I don't use git, so I don't feel qualified to say anything about whether or not the port should be renamed. If the maintainer finds it interesting, however, Randall Wood has implemented automated replacement for ports including colorscheme, hicolor-icon-theme and docbook-xml-412, so it can be done. Note that the approach in the latter of these is probably safer (I had problems with port hanging after trialling on another port the automated uninstallation scheme used in the first two), but it does mean that the user will have to manually remove the obsoleted port.

Thanks nonetheless to zacheryph for bringing the update to our attention; I look forward to seeing more patch submissions from you!