NAME


clean-binary-files - remove a third party binaries (JARs) from an upstream archive

SYNOPSIS


clean-binary-files {[-f {-, instructions_file}], [-e exclusion_file] [-l]} [-a archive_file] [-d custom_jar_map] [-n] [-p] [-s]

OPTIONS


-f The instructions file, specifying which files to keep and which to remove
-e The exclusions file, specifying special binary files that are to be preserved, or non-binary files that are to be removed.
-l Only list instructions (to put in instructions file), do not delete anything.
-a Archive file on which actions will be performed, as opposed to current directory
-d A custom jar map file (has priority over the generic one).
-n No symlinks (i.e. only clean jars, don’t run build-jar-repository afterwards)
-p Preserve original file names (-p to build-jar-repository)
-s Silent mode. Won’t output commands during cleanup
-f The instructions file, specifying which files to keep and which to remove
-e - The exclusions file, specifying special binary files that are to be preserved, or non-binary files that are to be removed.
-l - Only list instructions (to put in instructions file), do not delete anything.
-a - Archive file on which actions will be performed, as opposed to current directory
-d - A custom jar map file (has priority over the generic one).
-n - No symlinks (i.e. only clean jars, don’t run build-jar-repository afterwards)
-p - Preserve original file names (-p to build-jar-repository)
-s - Silent mode. Won’t output commands during cleanup

EXAMPLES


Suppose there is a vanilla tarball abc-1.tar.gz with some binary files (jars) in it. In the source repo, we would want a clean copy without any jars. We can use the scripts to achieve this:
To generate an instructions file:
clean-binary-files -e <exclusion file> -l -a abc-1.tar.gz > instructions
This creates an ’instructions’ file, which contains info on what stays and what goes.
Then, one can run:
clean-binary-files -f instructions -n -a abc-1.tar.gz
This would create abc-1-clean.tar.gz for uploading into jpp/fedora/etc. repositories with no binary (jar) files.
Alternatively, if you have a vanilla tarball, you can clean and create symlinks in it’s place all at once by:
clean-binary-files -e <exclusion file> -d <custom_jar_map> -a abc-1.tar.gz
Note: If the -a <file> is not given to clean-binary-files(1), all actions are performed on current directory.

SEE ALSO


Regular Manual Pages

check-binary-files(1), create-jar-\links(1), jpackage-utils(7)

Documentation

Further reading should be found in clean-binary-files.txt located in your standard documentation directory.
Original mail is here:
https://www.zarb.org/pipermail/jpackage-discuss/2005-November/009158.html

AUTHOR


Written by Deepak Bhole

REPORTING BUGS


Report bugs using JPackage Bugzilla (http://www.jpackage.org/bugzilla/)

openSUSE Logo

Contents