While testing my previous patches to allow for an NDB only build of RPM, I ran
across an issue using the --root argument.
When passing --root, the strace log shows that after the chroot call, a stat()
of the Packages.db absolute path fails, which triggers a reopen, which fails as
it attempts open(
Projects that use autoconf are expected to detect build prerequisites and
libraries.
This usually leads to a set of ad hoc de facto m4 macros that deal with various
details like API and path incompatibilities, much of which is platform and os
and distro dependent.
Various standard tools (like
After some further thought:
Using an embedded '_' character as a strong hint (e.g. "_python_sitelib") for
namespace membership, and adding a filter for those macros that do not have
conformant naming, is likelier a far less disruptive deployment than adding
Brand New! Better! Bestest! explicit
@n3npq Ooh, this looks very nice!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/256#issuecomment-316095214___
Rpm-maint maili
Here is a moderately complex real world example of how to use: detecting ZSTD
either externally or internally.
In configure.ac:
```
dnl # Facebook Zstd
RPM_CHECK_LIB(
[Facebook Zstd], [zstd],
[zstd], [ZSTD_versionNumber], [zstd.h],
[no,external:internal:none], [zstd:lib:lib],
[
The RPM_CHECK_LIB macro: add to acinclude.m4.
[rpm_check_lib.m4.gz](https://github.com/rpm-software-management/rpm/files/1156106/rpm_check_lib.m4.gz)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-sof
Projects that use autoconf are expected to detect build prerequisites and
libraries.
This usually leads to a set of ad hoc de facto m4 macros that deal with various
details like API and path incompatibilities, much of which is platform and os
and distro dependent.
Various standard tools (like
Closed #254.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/254#event-1168337543___
Rpm-maint mailing list
Rpm-maint@lists.rpm.o
Thanks! Pushed.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/254#issuecomment-316064237___
Rpm-maint mailing list
Rpm-maint@li
Thanks! Pushed.
Florian
On 07/17/2017 12:58 PM, Mark Wielaard wrote:
> Use --keep-section SECTION or --remove-section SECTION to explicitly
> keep a (non-allocated) section in the main executable or explicitly
> remove it into the .debug file. SECTION is an extended wildcard pattern.
> Both optio
Here are URL's for zstd, brotli, and lzfse"
- [https://github.com/facebook/zstd.git](url)
- [https://github.com/google/brotli.git](url)
- [https://github.com/lzfse/lzfse.git](url)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on Git
There are (at least) 3 new FSE compression formats that have been released in
the past few years: zstd (Facebook), brotli (Google), lzfse (Apple).
The new compressors have better compression ratios and speed than gzip/zlib.
And while then compression rations is still not as good as XZ/LZMA, the
12 matches
Mail list logo
