search

Backbase / bb-cli

Command line tools for working with Backbase CXP.
Other
32 stars 19 forks source link

import-item from windows to *nix #125

Closed igord closed 8 years ago

igord commented 8 years ago

import-item will use native windows lib to create zip That is apparently a problem as file paths inside a zip are not preserved properly http://unix.stackexchange.com/questions/166159/convert-a-windows-created-zip-to-linux-internal-paths-issue When we import a zip file created on windows, or import-item remotely from windows to *nix machine, it will fail.

The solution will be to use 7zip on windows, but that will require 7zip to be installed.

craigwalkeruk commented 8 years ago

@igord , you libs used current look to be doing it own compression, have you tried to use the windows native DOS command to zip.upzip?

igord commented 8 years ago

@craigwalkeruk are they available on all versions of windows that we support? we are using shelljs already so I could try...

craigwalkeruk commented 8 years ago

from windows 3.11 to 10.. i think. Even i expect windows powershell will do the same shell command

bartveenstra commented 8 years ago

Is there a solution for this already?

dirkgietelink commented 8 years ago

Some OOTB thinking... I've seen cases before, where zipping on windows causes very restrictive file permissions inside the archive once extracted on *nix systems. So, it might be the case the import fails because extraction goes fine, but the user not even having read permissions on some extracted files. So chmod might be needed. @bartveenstra have you check this?

bartveenstra commented 8 years ago

The problem is that it fails to do an import-item on windows to windows. No Unix paths yet. What we might think is the maximum path lenght in Windows. It was failing on importing jquery which has crazy nested directories..