[arch-general] Soft vs Hard links for man pages
Hi all, I was looking into bug FS#5392 [1] which details makepkg's inability to compress all man pages. Specifically, it fails when files are hard linked because gzip does not work on them. I have made a fairly simple fix for this. For a specific man page, it removes all other hard links, compresses the page and then regenerates the links. When the links are regenerated, is it preferable that they are hard linked again or should they be soft linked? I am leaning towards hard linked because that is the way they were upstream. However, the script I used to use to compress man pages in LFS had an option to turn them into soft links, so there must have been demand for soft links. Note that with soft links, it would be the first file found by "find" that everything would be linked to and that may seem strange in some contexts. Probably another reason to stick with hard links. Also, one of the comments in the bug report [2] mentions that bz2 files are not changed. I could at the same time add a change to convert these to gzip format but does that really matter? Both gzip and bzip2 are in core/base. Finally, now pacman has been moved to git I really have no idea how to create a diff! Can anybody suggest a good git cheatsheet? Cheers Allan [1]http://bugs.archlinux.org/task/5392 [2]http://bugs.archlinux.org/task/5392#comment15422
2007/12/3, Allan McRae <mcrae_allan@hotmail.com>:
Hi all,
[cut]
Finally, now pacman has been moved to git I really have no idea how to create a diff! Can anybody suggest a good git cheatsheet?
You can use git diff. Simply: git clone [address] pacman - Do your modifications - git diff > patch_to_send. There will be problems if remote repo is modified while you do your modifications; in other words, the patch that you make isn't synced with the remote repo. Bye
On Dec 3, 2007 8:05 AM, DaNiMoTh <jjdanimoth@gmail.com> wrote:
You can use git diff. Simply: git clone [address] pacman - Do your modifications - git diff > patch_to_send.
There will be problems if remote repo is modified while you do your modifications; in other words, the patch that you make isn't synced with the remote repo.
It's probably far better to do the following: git clone <url> git checkout -b mychanges #make a branch for yourself, and switch to it ... make your changes... git commit -a -s #commit what you did, and sign off git format-patch master #create a patch against the master branch (the original clone) The reason format-patch is superior here is that it maintains your authorship and change description.
On Dec 3, 2007 7:50 AM, Allan McRae <mcrae_allan@hotmail.com> wrote:
Finally, now pacman has been moved to git I really have no idea how to create a diff! Can anybody suggest a good git cheatsheet?
<http://wiki.archlinux.org/index.php/Super_Quick_Git_Guide> <http://www.kernel.org/pub/software/scm/git/docs/tutorial.html> If you've used SVN: <http://git.or.cz/course/svn.html>
participants (4)
-
Aaron Griffin
-
Allan McRae
-
Dan McGee
-
DaNiMoTh