|  | Commit message (Collapse) | Author | Age | 
|---|
| |\ |  | 
| | | |  | 
| |/  
|   
|   
|   
|   
| | common prefix among the $filenames list. This approach is used when the
 RPM package does not have a {bin,lib,lib64,include,share,sbin,libexec}
 subdirectory in order to create the symlinks from /opt to /Programs. | 
| | |  | 
| | 
| 
| 
| 
| | provided as input, we now list the contents of all RPMs at once to
determine how to create the /opt symlinks of the uncompressed packages. | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | possible that some of the RPM files processed will list some of the
other RPMs as their dependencies. Since all of them will be saved under
the same /Programs entry, it's pointless to record those on
Resources/Dependencies. This commit implements a filter using the
rpminfo utility to take that into consideration when producing the
Dependencies file. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | - Dependencies: if multiple RPM files are merged to a single entry under
  /Programs, then the deps of all packages are reported on this file;
- Architecture: always populated. 'uname -m' is used as fallback;
- Revision: always populated. When multiple RPM packages are merged to a
  single entry under /Programs, only the revision of the last package is
  stored on this file;
- PackageSource: this is a new file. It contains a [File] field with the
  name of the RPM file installed and a [Distribution] field that tells
  for which distro the RPM has been packed. When multiple RPM packages
  are given as input a blank line will separate each
  [File],[Distribution] pair. | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | |  | 
| | 
| 
| 
| 
| 
| 
| | all the files into the same entry under /Programs. When multiple RPM
files are provided and --app-name is not set, then each RPM file is
installed under its own entry under /Programs. The target directories
are chosen based on information extracted from the RPM files. | 
| | 
| 
| 
| 
| 
| | Restrict verbose messages to --verbose mode;
Catch more complex dependency strings when looking for the programs they
belong to. | 
| | |  | 
| | |  | 
| | 
| 
| 
| | /Programs. | 
| | 
| 
| 
| | attempt to search the web for package/dependency name resolution. | 
| | 
| 
| 
| | guessed. | 
|  |  |