clean-binary-files(1) [suse man page]

CLEAN-BINARY-FILES(1)						   User Commands					     CLEAN-BINARY-FILES(1)

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-ks(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/)

clean-binary-files (jpackage-utils) 1.7.5			   February 2009					     CLEAN-BINARY-FILES(1)

Check Out this Related Man Page

GIT-CLEAN(1)							    Git Manual							      GIT-CLEAN(1)

NAME

       git-clean - Remove untracked files from the working tree

SYNOPSIS

       git clean [-d] [-f] [-n] [-q] [-e <pattern>] [-x | -X] [--] <path>...

DESCRIPTION

       Cleans the working tree by recursively removing files that are not under version control, starting from the current directory.

       Normally, only files unknown to Git are removed, but if the -x option is specified, ignored files are also removed. This can, for example,
       be useful to remove all build products.

       If any optional <path>... arguments are given, only those paths are affected.

OPTIONS

       -d
	   Remove untracked directories in addition to untracked files. If an untracked directory is managed by a different Git repository, it is
	   not removed by default. Use -f option twice if you really want to remove such a directory.

       -f, --force
	   If the Git configuration variable clean.requireForce is not set to false, git clean will refuse to run unless given -f or -n.

       -n, --dry-run
	   Don't actually remove anything, just show what would be done.

       -q, --quiet
	   Be quiet, only report errors, but not the files that are successfully removed.

       -e <pattern>, --exclude=<pattern>
	   In addition to those found in .gitignore (per directory) and $GIT_DIR/info/exclude, also consider these patterns to be in the set of
	   the ignore rules in effect.

       -x
	   Don't use the standard ignore rules read from .gitignore (per directory) and $GIT_DIR/info/exclude, but do still use the ignore rules
	   given with -e options. This allows removing all untracked files, including build products. This can be used (possibly in conjunction
	   with git reset) to create a pristine working directory to test a clean build.

       -X
	   Remove only files ignored by Git. This may be useful to rebuild everything from scratch, but keep manually created files.

SEE ALSO

       gitignore(5)

GIT

       Part of the git(1) suite

Git 1.8.3.1							    06/10/2014							      GIT-CLEAN(1)

Linux and UNIX Man Pages

clean-binary-files(1) [suse man page]

Check Out this Related Man Page