http://bugs.winehq.org/show_bug.cgi?id=5985
------- Additional Comments From saulius.krasuckas@elst.vtu.lt 2006-18-08 09:06 ------- Regardless of a state of this bug I think it has its own value as it shows conflicts of some interests. Some of my sophistics:
Jesse wrote: | Building git is beyond wine.
I agree, but (as Peto notes correctly) our wiki pushes user on building it from a source.
Peto wrote: | I sticked with the manual, thinking "if they recommend compiling the Git, then | it's probably the best way to go".
Right, Peto, but I guess you can easily understand that all the texts of *.winehq.org can be divided into a 4 parts:
1, main site (www.*); 2, appdb site (appdb.*); 3, wiki site (wiki.*); 4, bugzilla site (bugs.*).
The dynamics of a content of each site increases with its number here. That has own reasons. Changes to the main site are crucial and every change goes through a single www-maintainer.
Changes to the appdb depends mostly on several dosens of app maintainers, so content gets more dynamic.
Changes in Wiki occurrs whenever any developer or contributor feel a need to share some fresh and interesting info with all the community of devs. Here are no strict content maintainers as everyone tries to get his best, IMHO.
And probably this is why you got confused by this quote:
Wine Wiki writes: | | 2.1. Downloading and installing | | Download the latest version of GIT from [WWW]. Compile and install it. | It installs into ~/bin by default. You may need to use the make option | "WITH_OWN_SUBPROCESS_PY='YesPlease'" if you have Python < v2.4. | Be sure also to have merge program available (usually it comes with RCS).
This clearly asks for a separate Wiki page about getting GIT installed. There are several linux distributions, several ways on each to get GIT binaries on disk.
Now that you have got into the conflict epicenter and by looking at the idea of a Wikies I conclude that namely you, Peto, should do the required changes :) or at least post relevant text for both WineGIT page and a new, separate subpage about GIT installation. For example:
"Try to get GIT in an way ordinary for your distro: * Debian: apt-get install git-core * FC: yum install git * Gentoo: ... Compile GIT and install it only when you know what you are doing or at least when you have problems with packaged binaries. =)"
With such new page every newbie who uses another undescribed distro could easily spot the problem (and probable change it by itself). And editing Wikies isn't really hard, IMHO; there is a sandbox for testing your skills in our Wiki.
| If just a mention took place ("For debian systems, it might be better to | download the package and install it using dpkg -i <package>), I'd do | it and spare You and me this trouble ;o)
You've downloaded package manually and used dpkg to install it. Peto, did the Alexandre's advise not work? (apt-get install git-core)
| When You compile Git from sources (as suggested in GitWine manual), You need | them. See git's INSTALL for more info. Hint: cannot do "configure" without | autoconf before. Next, documentation needs asciidoc. And needs more than that, | so that I resigned compiling docs for git (in contradiction to manual).
Hey, this is somewhat generic stuff about building software under unix-like OSes. But you could put that into separate Wikie page too, lets call it GitInstalling.
| Proxy system variable I consider "must have" | for significant part of git users.
And that would go here too.
| And Debian users need to know, that compiling from sources | is not the best way for them.
Well, yes, and I am not a Debian user, but every Debianist IMHO probably should know (by reading manual and from its experience) that this is distro for pendatic admins who de facto don't like compiling from a source and prefer automated package installing based on official distro's database. Probably that's why no one had given directions for debianists in the WineGIT page. No?
| However, I really don't want to know "everything about git"! :-) I use the | "how to do regression testing with git" manual.
Hey, OpenSource world is too big and too interrelated to get exactly right part of information ;-) If you don't like the situation, change it, please. For example contribute to the Wiki of project. That's what are Wiki engines designed for.
Of course, I hadn't touch the 4th item, a bug reports ;-) This is most dynamic area of Wine related texts. If you contribute to this, 4th level, what would stop from doing the same to the 3rd level? I guess, nothing Good luck, Peto :)
-
Wine Bugs