Am Dienstag, 28. September 2010, 08:23:56 schrieb brook.hong(a)nokia.com:
You can use
regexp, so for example "libzip*tar*".
But maybe it would make sense to extend tar_scm to copy out defined
files directly to avoid the
extra extraction step.
And I find another issue in the extract_file script just now.
With tar_scm, a directory is added into the tar file as a root.
In the extract_file script, it uses `tar xfj "$existing_archive" $MYFILES`.
Then a path must be included in $MYFILES.
But the path was removed by a ## pattern in the script.
Yes, there is also a general problem with bs_service daemon which leads to the
problem that service X can not obsolete files from service Y in all cases.
That is something I need to fix first for 2.1.
To support that, I plan also to modify the naming of the files from
Thus extract_file can never extract file from the tar file generated by tar_scm.
Adrian, will you or anyone else fix this issue and another issue(mentioned in another
mail)? Or extend tar_scm?
I would be happy to extend tar_scm, but I am time limited atm. So it would be great if
can provide a patch (or direct submitrequest to openSUSE:Tools:Unstable).
There is also the request to clone files directly without tar-ing them (to support
distros who maintain their files in svn/git directly).
Therefore I was also considering to rename tar_scm to something like
add the tar functionlity optional to it. Because I like to avoid to copy the git/svn
functionality into another service.
Would be great if you or anyone else could think about this approach and deliver a
SUSE Linux Products GmbH
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org