[CentOS] PHP version not enough for developers

[Michael Hennebry]

>From https://lists.centos.org/mailman/listinfo/centos :
> CentOS -- CentOS mailing list
>
> 
> About CentOS 	English (USA)
>
> This is a General discussion list for all issues CentOS. Security updates are currently announced on this list once daily. This list is read and reply for anyone that is a member of the mailing list.
>
> To see the collection of prior postings to the list, visit the CentOS Archives.

On Mon, 26 Oct 2015, Johnny Hughes wrote:

> On 10/26/2015 12:19 PM, Michael Hennebry wrote:
>> On Sat, 24 Oct 2015, Johnny Hughes wrote:
>>
>>> On 10/23/2015 03:44 PM, m.roth at 5-cent.us wrote:
>>>> What FUD? It adds *binary* logfiles, readable only with a separate
>>>> program; when I restart a service, it does not *tell* me what's going
>>>> on,
>>>> just worked or didn't, so I don't know, if it fails, where, the messages
>>>> from journalctl are extremely unhelpful, and when it boots, if I want to
>>>> watch, it tends to hide much info. It's much less informative in most
>>>> ways
>>>> in helping me solve problems.
>>>>
>>>
>>> Jesus Christ .. do we really have to start ANOTHER systemd thread.
>>
>> Yes.
>>
>>> These lists are for providing USEFUL information to CentOS users ..
>>
>> Let's get some information that might be useful:
>>
>> Are binary logfiles an inherent part of systemd?
>> If so, equating systemd with the devil would seem appropriate.
>> My expectation is that it is not.
>>
>> Is the aforementioned dearth of information an inherent part of systemd?
>> If so, equating systemd with the devil would seem appropriate.
>> My expectation is that it is not.
>>
>>
>> The evil of binary journals for people is fairly cut and dry.
>> If data is only for another program,
>> making it binary when it could easily be text is against
>> unix philosophy and a bad design choice, but not proof of evil.
>> When the data is text specifically to be read by people,
>> choosing to make it binary is evil and rude.
>
> All of that might be true, however this is not the place to discuss that.

Of course this is the place to whine about systemd
threads when journalctl is under discussion.

> The goal if CentOS is to exactly build RHEL's source code.  We do that.
> If that is not what you want in a Linux distribution, then CentOS is
> not for you .. that is just the facts.
>
> We are not going to change something that is designed a certain way in
> RHEL source code.

The contents of /etc/ssh/ssh_config ?

Other post-install modifications are certainly possible.
A demon that continuously makes text copies of the journalctl logs?
A replacement for journalctl?

> So, that means that the place to have those discussions is not on a
> CentOS list, but on a list where something can be done about it.  On the
> list where the code is actually developed, on a Fedora List or a RHEL list.
>
>
>>
>>
>>> flame threads will result in list users who are moderated.
>>
>> E.g. Johhny Hughes?
>>
>> What do threat posts result in?
>>
>
> That is not a threat, it is a promise.  I set the moderation bits on the
> list.  I get dozens of emails off list asking for people to moderated on
> the flame fest emails.

Call it a promise if you want.
Denying that it is a threat is a bit much.

> We should all be adult and professional enough to understand that
> designing of software happens somewhere else and endlessly complaining
> about it here does nothing to get it fixed.  It just annoys users who
> want to use centos and get help using it.

-- 
Michael   hennebry at web.cs.ndsu.NoDak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
                                                              --  someeecards