On 19 July 2012 03:41, James Paige <b...@hamsterrepublic.com> wrote: > On Thu, Jul 19, 2012 at 03:18:54AM +1200, Ralph Versteegen wrote: >> On 19 July 2012 02:18, James Paige <b...@hamsterrepublic.com> wrote: >> > On Thu, Jul 19, 2012 at 01:21:27AM +1200, Ralph Versteegen wrote: >> >> On 18 July 2012 09:52, <subvers...@hamsterrepublic.com> wrote: >> >> > james >> >> > 2012-07-17 14:52:04 -0700 (Tue, 17 Jul 2012) >> >> > 297 >> >> > Add a script that creates ohrrpgce-mac-minimal-linkless.tar.gz based on >> >> > ohrrpgce-mac-minimal.tar.gz >> >> > The resulting file is over 300% larger, but this seems to be the only >> >> > workaround for distributing a Mac >> >> > App bundle from a Windows computer. (Other platforms still use >> >> > ohrrpgce-mac-minimal.tar.gz) >> >> > --- >> >> > A web/ohr-mac-linkless.sh >> >> >> >> I'm confused. Where is tar.exe? It's not in wip/support or mentioned >> >> in any of the build scripts. Do Windows users have to install msys or >> >> cygwin in order to use certain Distribute Menu features? I admit that >> >> I still have barely touched it. >> > >> > It is located at http://hamsterrepublic.com/ohrrpgce/support/tar.zip and >> > custom.exe downloads it using the included wget.exe the first time you >> > try to use it. >> >> Thanks; finally I found the relevant code well hidden in >> find_helper_app. After so many years spent learning the maze-like >> nooks of the source, it's disconcerting to again be totally lost and >> unable to find something! > > Any code you haven't looked at might as well have been written by > somebody else-- this is doubly true when it actually /was/ written by > somebody else :)
I read this as "Any code you haven't written might as well have been written by somebody else...," so I was confused by the doubly used doubles :) >> >> (I just finished my MSc yesterday >> >> after a gruelling few weeks of last minute panic; I will probably be >> >> on break a while longer before getting back to serious OHR >> >> development). >> > >> > Congratulations! Enjoy your rest! :) >> > >> >> I assume you are using msys's tar. I had a look at the source. I'm >> >> rather shocked to see that it was forked from GNU tar in 2001, and >> >> since then GNU tar has received literally hundreds of bugfixes and new >> >> features, while the msys fork has only had 4 commits. So I intend to >> >> see what we can do to get a modern GNU tar on Windows. I might even >> >> try my hand at implementing some feature to allow us to preserve >> >> symlinks on Windows. >> > >> > I think I ended up using the tar.exe from UnxUtils. I did try msys's >> > tar.exe too, but they both had the same horrible limitations, so I went >> > with the UnxUtils one because it had no .dll dependencies. >> > >> > A new tar tool would be great! >> >> So what are the other problems with tar.exe aside from buggy >> extracting of symlinked files? Why did you want support for --owner >> and --group? > > --owner and --group are important for building the .deb packages. The > files in control.tar.gz and data.tar.gz are expected to have the same > owner/group as they would have when they are installed (which almost > always means root:root). The UnxUtils tar.exe puts in dummy values of > user/group so when you install the Debian package it warns you "This > package is of bad quality" although forcing it to install anyway works, > and the files get installed with the correct root/root ownership based > on the ownership of the existing directories that they are getting > installed into. > > One of the tar.exe that I tested had no support whatsoever for --owner > and --group, and another I tested attempted to support them, but by > mapping to actual Windows user accounts, which I guess would be a > non-stupid thing to do if you were using tar exclusively to backup and > restore on Windows, but cannot possibly ever be the right thing to do if > you are trying to use tar in a cross-platform way. > > The other feature I would have liked to see would be the ability to turn > on the executable bit on certain files. There is the --mode command line > argument, but that sets the mode for ALL files, I couldn't find any way > to set the mode selectively for only certain files. So using --mode changes the mode of all files already in an archive instead of only the ones you're adding? > --- > James > _______________________________________________ > Ohrrpgce mailing list > ohrrpgce@lists.motherhamster.org > http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org _______________________________________________ Ohrrpgce mailing list ohrrpgce@lists.motherhamster.org http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
