[Bug 559856] Review Request: libbsd - Library providing BSD-compatible functions for portability

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=559856

--- Comment #12 from Kevin Kofler <kevin@xxxxxxxxxxxxxxxx> 2010-01-31 02:30:38 EST ---
And I don't see how /usr/include/vis.h and /usr/include/libutil.h would be a
problem:
* they don't conflict with any other package in Fedora,
* they are implementations of the headers usually named that way, not some
unexpected conflicting headers squatting the names,
* the "inconsistency" is because obviously you can't replace standard glibc
headers with BSD ones.

That said, -isystem /usr/include/bsd is not going to work as expected because
the headers don't include the glibc ones. This is bad for portability, you have
to patch programs to add extra #include statements. IMHO, the headers should be
doing:
#include_next <string.h>
(or the respective header, of course) so you can use -isystem /usr/include/bsd.

One solution could be to provide a separate /usr/include/libbsd which provides
headers of the form:
#include_next <string.h>
#include <bsd/string.h>
That way your libbsd package is compatible with upstream, but you can also
easily port existing BSD programs with -isystem /usr/include/libbsd.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review

[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]