Bad practise is the only practise if knowledge about good practise is
not available.
I am fully prepared to accept you are right. In fact, in my professional
settings I would not do otherwise.
But this is a special case, for a huge platform, and somebody, somehow,
forgot about the license....
Because the starting compiler for Raspbian is not available......
That's the point:
In war ( I am a former tank commander when it was still relevant for an
19 year old) You improvise when resources are not available.
I agree with you. Get it?
But where's the stuff we can use to do it properly? My stuff works, is
based on trunk, but not usable?
Ofcourse not.
This goes to the core of the project: either one sticks to the rules, or
one deviates from it.
This is a blatant case of GPL ignorance, since the starting compiler is
not made available.
And the compiler is GPL'd
THAT'S my point.
On 10/23/2014 11:16 AM, Jonas Maebe wrote:
On 23/10/14 11:09, Thaddy de Koning wrote:
On 10/23/2014 11:04 AM, Jonas Maebe wrote:
On 23/10/14 10:55, Thaddy de Koning wrote:
Plz advice on how to progress,
By never saying that people should build trunk with trunk.
Which means you shut out the platform.
I'm not saying you can't provide any downloads, nor that Debian/Raspbian
must remove their custom patched 2.6.4 releases. I'm only saying that
you should never encourage people to build trunk with trunk for the
reasons that I have explained many times before.
Which is a teaching platform.
So don't teach them bad practices that will get them into trouble.
Jonas
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist - [email protected]
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
