On Mon, Aug 25, 2008 at 02:21:54PM -0700, Junio C Hamano <gitster@xxxxxxxxx> wrote: > The real question was about if/why that git repository _has to be_ outside > of /usr/lib/*/Pootle/. Is that because --work-tree, if worked properly, > would have allowed it to be, or is that because for some external reason > you are not allowed to have .git under /usr/lib/*/Pootle/ directory? I'm not 100% sure, but I think the reason is that Pootle runs as the user 'pootle' which has write access to some /var/pootle or /home/pootle dir, but has no write access to /usr/lib/*/Pootle/. > If the latter, that shows the real requirement to keep supporting it as a > feature, and issues around it need to be fixed. Otherwise, i.e. if it > does not require use of --work-tree but it uses it only because it could, > that gives us less incentive to keep --work-tree as a feature. I think this is the latter, though as I mentioned previously - it can be still worked around by a "cd /other/path; git <command>; cd -" (speaking in shell commands), so it is not a "must", it would be just ugly IMHO.
Attachment:
pgpSXgyGxIThX.pgp
Description: PGP signature
