[Bug 195647] Review Request: redland

[bugzilla at redhat.com]

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

Summary: Review Request: redland


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





------- Additional Comments From rc040203 at freenet.de  2007-02-12 07:54 EST -------
(In reply to comment #11)
> wrt. 5:

> - there is nothing as such wrong with installing headers in /usr/include, it is
> merely a style issue.
Sorry, this is not a "mere style" issue.

- It affects effectiveness of compilers when searching /usr/include (N
files/dirs more to stat).
- It raises the potential of file conflicts.
- /usr/include is "special"

ONE package isn't much of a problem, but 10's or 100's are.

>  While I personally much prefer projects that care about
> these issues and use subdirectories, and do so in my own projects, it is IMO not
> a requirement and not a maintainer's call to make.  I personally get hugely
> annoyed when a downstream packager does something to one of my projects that
> really should be the maintainer's call.

My position is opposite:
* /usr/include is the "system-include" directory and should largely be reserved
to essential system packages (Many of them are covered by standards, e.g. POSIX).

* In many cases, upstream doesn't care about this because they assume their
package to be installed into a "per package" hierarchy (/opt/<package> or
similar) so they aren't aware about the issues their habits could cause.

* I consider a maintainer who is not able to work around this or unwilling to
address this issue, to be acting a careless and negligent (I am waiting for the
day, somebody installs a file named "stdint.h", or "list" to /usr/include)

>  Changing stuff like this is a cost to
> users/developers of the package that gets paid by the upstream maintainer, not
> the packager.
CPPFLAGS=-I/usr/include/<package>

> - further examples of packages on my system that install headers in /usr/include
> directly: gd, gmp, libidn, libjpeg, js, mx, openldap, libodbc, pilot-link,
> libtiff, libtermcap, zlib
Yes, many of them all in the same boat, but .. many of them are out of control
of Extras.

Some of these packages however have evolved into "essential system libs" (e.g..
zlib) which would justify installing their headers to /usr/include, redland
definitely is not one of these.

Also, you should be aware that FE-policy so far had been, headers can go to
"/usr/include, if a package installs very few headers which are almost
guaranteed never to conflict".

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.