sorry for being such stupid, what do you mean with /usr/local/lib/{lcl,codetools,synedit}? i don't think i have anything in /usr/local/lib/ and at the moment i do not want any lazarus files to be there and of course i don't want any lazarus stuff in my /etc/ plz enlighten a stupid creature like me and tell me what the problem is with the existing installation process (or is this just an issue for making a lazarus multi-user installation?)

satan

Hi

Also too me.
Is anybody familiar with Linux Filesystem Standard? Think the suggested layout would comply with it but I'm not sure.

bye,

Stefan

Hi all,

I think, the current 'make install' has some drawbacks.

1. The term 'install' is not very good. It is a run only installation without sources.
2. The ppu/o files are splitted up into /usr/local/lib/{lcl,codetools,synedit}. How can the Makefile.fpc be changed to combine them under a lazarus dir?
3. The IDE needs the sources. IMO lazarus is not a standard application which just needs a binary and some resource files. A development environment needs the sources as examples and for coders to look up, what is not documented (that is at the moment nearly everything).

So, a proper installation of the IDE is:
- the complete source tree
- a link to /usr/bin/lazarus
- some default option files in /etc/

Comments!

Mattias

2. The ppu/o files are splitted up into /usr/local/lib/{lcl,codetools,synedit}. How can the Makefile.fpc be changed to combine them under a lazarus dir?

When you install it under
/usr/local/lib/lazarus/{lcl,codetools,synedit,...} then you can use -Fu/usr/local/lib/lazarus/* in the fpc.cfg. And for the Makefile in will be UNITDIR+=$(wildcard /usr/local/lib/lazarus/*)

Peter

Hi

Menu's are already working in lcl (look at examples) and I'm currently working on them. Current status

- after a menu is created (displayed) no further items can be added (assume this is because the RecreateWnd function is missing)
- streaming is almost working in my local source tree and will be submitted as soon as I can fix 2 remaining issues (approx. 1 week)
- menu-editor seems a little bit complicated at the moment. I set up a basic dialog to make this work but have no timeframe yet.

bye,

Stefan

These locations should only be used for .RPM package (even though this RPM would not be a part of the distro.

Locally compiled stuff should always default to /usr/local/share and /usr/local/lib respectively.

BTW, even the RPM should install to /usr/local/* (by FHS), as it is not a vendor supplied package (but it is too common to install just to /usr).

For more info, see http://www.pathname.com/fhs/

Michal

That's right. But there are various ways to install the fpc sources. Perhaps a Quick Installation & Setup should be added to the web site, which explains two or three possibilities to install fpc and lazarus. (cvs, zip, multiuser, singleuser)

and what about the ppu/o files (if they will be in one directory) in /usr/lib/lazarus and the rest including source in /usr/share/lazarus?

Sounds good to me.

Mattias

Matthew Bradford wrote

I was just wondering if there was a date in the foreseeable future when Lazarus would be complete?

Picking a date would be next to impossible. The problem is due to lack of developers. There are very few of us and even the few of us can only contribute off and on as the year goes along. Right now the majority of the work is being done by Mattias and Marc. Last year at this time it was a different set and probably next year at this time it will be still another set. When we originally started Lazarus we didn't invision that it would have even took this long but alas it has. So to pick a date as to it's completion is very problematic.

And until then... any clues as to when the menu creator might be well.. created?

Maybe you can lend a hand with writing it. :-)

I have changed it to <lib dir>/lazarus/{lcl,codetools,synedit}. The lib directory is OS dependent and automatically set by fpcmake. I'm also not very happy with /usr/local/lib.

and of course i don't want any lazarus stuff in my /etc/ plz enlighten a stupid creature like me and tell me what the problem is with the existing installation process (or is this just an issue for making a lazarus multi-user installation?)

Yep. For multi user.
When the IDE can't find a config file in the user dir, it will copy the template file from /etc/lazarus/ (under linux, see <lazdir>/include/<OS>/lazconf.inc).

Mattias

These locations should only be used for .RPM package (even though this RPM would not be a part of the distro.

where do you got the idea that these are only for .RPM packages (btw not every distro uses RPM)?

quote:

'Any program or package which contains or requires data that doesn't need to be modified should store that data in /usr/share (or /usr/local/share, if installed locally). It is recommended that a subdirectory be used in /usr/share for this purpose.'

this would mean that your /usr/local/share is ok, but i would like to see it in /usr/share since it is common to install stuff there (and as i quoted there is no difference if it is a package or program) i think we should place it just where most people want it

Locally compiled stuff should always default to /usr/local/share and /usr/local/lib respectively.

another quote:

'/usr/lib includes object files, libraries, and internal binaries that are not intended to be executed directly by users or shell scripts.

Applications may use a single subdirectory under /usr/lib. If an application uses a subdirectory, all architecture-dependent data exclusively used by the application must be placed within that subdirectory.'

so i think there is no prob with this dir

but you are right that fhs says it should not must :) be installed to /usr/local (either /lib or /share for our purpose) to avoid it being overwritten by system updates since i don't think that anything in my /usr dir ever got overwritten by system updates i want stuff in the directories i mentioned in my first mail, just because they are common if you people want it in /usr/local so it follows the fhs put it there i think it's only little difference

but when i see things like this:

'For historical reasons, /usr/lib/sendmail must be a symbolic link to /usr/sbin/sendmail if the latter exists'

i don't know if it's better to go the fhs way or the common way

comments, please

Stefan,
RecreateWnd function does exists, it just needs to be called when a new item is added.

Shane

Hello,

Sorry for being rpm centric:-) (I am a Mandrake user, hah!) It of course applies to any precompiled package.

The common way is IMHO FHS compliant, and is what I actually try to say: if you do a make; make install from a tarball, default to /usr/local*, any :-) precompiled package should install to /usr*. At least I think it is common, as about any package I compile defaults to /usr/local* (only few to /opt, which I hate).
So I think we have the same opinion, including the /share and /lib dirs.

Perhaps autoconf stuff could be used here as well for user to have a possibiliy to choose.

Michal

what's with the fpc sources?
i thought they were needed by lazarus also
is there a standard directory where they are placed? i don't think so
and i think since they are needed, they also belong to a proper lazarus installation and what about the ppu/o files (if they will be in one directory) in /usr/lib/lazarus and the rest including source in /usr/share/lazarus?

666

I was just wondering if there was a date in the foreseeable future when Lazarus would be complete?

And until then... any clues as to when the menu creator might be well.. created?

All in all I can't tell you guys how cool this is. Congrats on a good project.

- Matt