now the interface will properly indicate that the archive is not writable
when that is the case (it was not even before the port to KArchive)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
fixes creating of archives with large files that cannot fit in /tmp (or
whatever the temporary directory is set to). note that this still depends
on how much space is available on the filesystem the archive is created on
and will not work for remote archives - remote archives will have to be
fetched somewhere with enough space to hold the archive and a copy of it
(possibly $HOME) but that is for another commit (currently archives are
fetched into /tmp but not uploaded upon modification)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
if you are not doing full rebuild (to catch API changes) atleast on
every new release then you are doing something wrong anyway
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
make it protected so that it is reusable and implement permissions
for LibArchiveInterface via it while at it
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
other changes such as syncing properties, updating some of the URLs,
adding missing feature information, removing of redundant checks and
variables and indentation were done in the process while testing if the
changes work as intended.
replacing find_package() with macro_optional_find_package() was also done
where applicable however it's usage is questionable due to the CMake
`CMAKE_DISABLE_FIND_PACKAGE_<PACKAGE>` option.
there is a lot to be done, mostly updating package properties so I am
thinking of either providing a package properties file (like the
MacroLibrary) which sets properties for packages globablly or setting
package properties from the CMake modules shipped with kdelibs. the first
solution may override properties for packages if other projects define them
however a check to ensure that is not done should suffice. the second
solution will cover only DESCRIPTION and URL meaning PURPOSE and TYPE will
still have to be specified in the build systems.
Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
this ensures tarballs with .tar.gz extension, for an example, will not be
opened and displayed as .tar archive containing other archive
Signed-off-by: Ivailo Monev <xakepa10@laimg.moc>
nowdays .tar.gz and .tar.bz2 files are recognized as
application/x-bzip and application/x-gzip respectively.
also added application/x-gzip-compressed-tar because
application/x-bzip-compressed-tar is in the list and I
think that's a legacy one but should not hurt.
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
