[Lazarus] Lazarus Release Candidate 1 of 1.4

Giuliano Colla giuliano.colla at fastwebnet.it
Thu Feb 19 13:44:03 CET 2015

Il 19/02/2015 12:32, Juha Manninen ha scritto:
> On Thu, Feb 19, 2015 at 1:10 PM, Giuliano Colla
> <giuliano.colla at fastwebnet.it> wrote:
>> Whatever it was, it's got fixed in the meantime.
> You installed it as root to a place where your normal user has no write access.

Then there's a bug, because the full scenario is:

The lazarus tree installed from rpm is in /usr/lib (or /usr/lib64) where 
normal user has no write access.
A custom executable is on ~/.lazarus_1.4 (--pcp= etc) where normal user 
has write access.
A "Build Lazarus" should therefore build a new custom executable in 
~/.lazarus_1.4 where the normal user has write access, and actually it does.

Given this scenario, the only place where a "clean all" needs to work is 
on the writeable local tree: if sources are located on a non writeable 
path is not relevant.
Without a "clean all", a number of stale ppu's where left in place in my 
writeable path.
I could build only by removing by hand ppu's in my writeable path.

The appropriate check should be if the *target* path is writeable. If 
it's not, then it's impossible to build. If it is, then it's possible to 
clean it in any way: automatically, clean common, clean all.


More information about the Lazarus mailing list