#1564 closed defect (invalid)
kdelibs and PCRE
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | BOOK | Version: | ~CVS |
| Severity: | normal | Keywords: | |
| Cc: |
Description
It should be mentioned in BLFS that --disable-pcre must be added to the configure command for kdelibs if you don't have pcre, or the configure will fail.
Change History (4)
comment:1 by , 19 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 19 years ago
Not that I don't agree with you that the bug is invalid. But should not this POLICY be clearly STATED in the book? (Maybe it is but I can't find it).
Or is this another one of those 'it's obvious to me, so you are a rather stupid person if it isn't obvious to you' things.
BTW, it isn't obvous to me.
comment:3 by , 19 years ago
What is not obvious to you?
Some time ago, and it could probably be found in the archives, I asked about this. I believe that bottom line was that "Recommended means that BLFS suggests to do this for a clean and trouble free build, that won't have issues either during the build process, or down the road at run-time.
Reasoning being is that if we provide instructions to do something that contridicts our "recommendation" it then makes our "recommendation" questionable. If we "recommend" to do something, we should expect that our advice is followed.
I just don't think we should make provisions for folks that don't wish to follow our recommendations. This, to me, would open up a big can of worms.
Perhaps we should open the discussion up over in -dev so that we can get more input?
Closing this bug as invalid. PCRE is on the recommended dependency list. If a builder chooses not to follow our recommendations, then whatever happens is on the builder.
Recommended = Do it
The only reason it is in recommeneded instead of reqiured is for technical accuracy. However, the BLFS instructions are written in the anticipation that builders will follow the recommendations.