All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergio Callegari <sergio.callegari@gmail.com>
To: git@vger.kernel.org
Subject: Followup: management of OO files - warning about "rezip" approach
Date: Sun, 14 Dec 2008 13:08:24 +0000 (UTC)	[thread overview]
Message-ID: <loom.20081214T123442-862@post.gmane.org> (raw)

Hi, some times ago, i considered ways to achieve a smarter management of
openoffice files with git.

The thread started at:

http://article.gmane.org/gmane.comp.version-control.git/95951

There, a "rezip" script was proposed to store OO files uncompressed into git
repos, so that the compression and delta machinery of git could operate at its
best with them.

Appartently, the script rose some interest.  In the following days I received
quite a few corrections/enhancements proposals for which all the posters I thank.

Also I was asked to upload the script and instructions relative to its adoption
together with .gitattributes to the git wiki.

This I didn't do (I do not know if someone else might have done it) because I
first wanted to be absolutely sure that the script would cause no problems to
anybody.

Unfortunately, I now see that there is an issue, so I am sending a warning.

The problem stems from the fact that ODF files, due to the zip compression also
might store pieces of info that are completely irrelevant.  For instance zip
stores ownership of member files.  This is why in the rezip script I initially
started to unzip files with -X.

Now, this seems to be looking for trouble when repos are passed from one user to
another one.

When we uncompress and ODF file for storing we should probably scrap away the
member ownership info alltogether. Note that this is not equivalent to not using
-X.  Not using -X would mean "changing" member owernership when an ODF file is
passed from one user to another one.  Using -X seemed to me the correct thing to
do as it allowed to leave untouched the member ownership.  However, -X fails
when user A has no permission to create files as user B.

I found out about this issue by having accounts on many hosts, where my
alphanumeric user ID maps to different numeric IDs.

I will look better at this as soon as I have time.  So far, please just be
careful.  My guess is that we should not use -X on "unzip" but use it on "zip".

E.g. patch the rezip script so that

PROFILE_UNZIP_ODF_UNCOMPRESS='-b -qq'
PROFILE_ZIP_ODF_UNCOMPRESS='-q -r -D -0 -X'
PROFILE_UNZIP_ODF_COMPRESS='-b -qq'
PROFILE_ZIP_ODF_COMPRESS='-q -r -D -6 -X'


Sergio

             reply	other threads:[~2008-12-14 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14 13:08 Sergio Callegari [this message]
2008-12-15 14:41 ` Followup: management of OO files - warning about "rezip" approach Peter Krefting

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20081214T123442-862@post.gmane.org \
    --to=sergio.callegari@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.