CLEAN-BINARY-FILES
NAMESYNOPSIS
OPTIONS
EXAMPLES
SEE ALSO
AUTHOR
REPORTING BUGS
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/)
More Linux Commands
manpages/hunspell.5.html
hunspell(5) format of Hunspell dictionaries and affix files
hunspell.5 - Hunspell(1) Hunspell requires two files to define the way a language is being spell checked: a dictionary file containing words and applicable flag
manpages/endrpcent.3.html
endrpcent(3) - get RPC entry (Library - Linux man page).....
endrpcent.3 - The getrpcent(), getrpcbyname(), and getrpcbynumber() functions each return a pointer to an object with the following structure containing the bro
manpages/cmsg.3.html
cmsg(3) - Access ancillary data (Library - Linux man page)
These macros are used to create and access control messages (also called ancillary data) that are not a part of the socket payload. This control information may
manpages/Mail::SpamAssassin::Plugin::WhiteListSubject.3pm.html
Mail::SpamAssassin::Plugin::WhiteListSubject.3pm............
This SpamAssassin plugin module provides eval tests for whitelisting and blacklisting particular strings in the Subject header. The value for whitelist_subject
manpages/isql.1.html
isql(1) unixODBC command-line interactive SQL tool..........
isql is a command line tool which allows the user to execute SQL in batch or interactively. It has some interesting options such as an option to generate output
manpages/perlvos.1.html
perlvos(1) - Perl for Stratus VOS - Linux manual page.......
This file contains notes for building perl on the Stratus OpenVOS operating system. Perl is a scripting or macro language that is popular on many systems. S....
manpages/gsnd.1.html
gsnd(1) - Run ghostscript (PostScript and PDF engine) withou
This script simply invokes gs(1) with the -NODISPLAY flag, followed by any other arguments from the command-line. SEE ALSO gs(1) VERSION This document was last
manpages/set_menu_init.3menu.html
set_menu_init(3menu) - set hooks for automatic invocation by
These functions make it possible to set hook functions to be called at various points in the automatic processing of input event codes by menu_driver. The funct
manpages/XvQueryEncodings.3.html
XvQueryEncodings(3) - return list of encodings for an adapto
XvQueryEncodings(3) returns encoding information about an adaptor. Each encoding is described by the XvEncodingInfo structure described above. The encodings are
manpages/mt.1.html
mt(1) - control magnetic tape drive operation (Man Page)....
This manual page documents the GNU version of mt. mt performs the given operation, which must be one of the tape operations listed below, on a tape drive. The d
manpages/snmp_sess_select_info.3.html
snmp_sess_select_info(3) - session functions (Man Page).....
These functions define a subset of the API that can be used to manage single SNMP sessions in a multi-threaded application. Except for snmp_sess_session(), thes
manpages/dfbg.1.html
dfbg(1) - DirectFB background configuration tool (Man Page)
dfbg is a small utility to configure the background of the DirectFB desktop. It loads the specified image and sets it as background image. dfbg requires DirectF
