Re: [lazarus] Lazarus packaging
On 31/01/2008, Ales Katona [EMAIL PROTECTED] wrote: If you mean that the package sources are installed read only: yes I mean that you install lazarus from a .deb into eg: /usr/lib/lazarus and that people can still install 3rd party components into this lazarus in some way (I realize that packaged components would conflict tho, because of the one binary problem, but that's a bit different beast) Yes, it's possible to have Lazarus somewhere and add-on packages (or components) somewhere else. I used to have Lazarus source in /opt/lazarus (readonly) and some add-on packages in /home/me/progra/mycoolpackage/ and it worked fine. When you installed and compiled Lazarus it installs (I think) default to ~/.lazarus/ directory. You can specify any output directory in the Build screen as well. Regards, - Graeme - ___ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/ _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Lazarus packaging
Ales Katona wrote / napísal(a): 2. I think lazarus should get separated into lazarus-lcl-widgetset packages, lazarus-ide and lazarus-tools (lazbuild and friends) with a dummy all-package like lazarus and a dummy lcl package which will simply default to per-distro widgetset (eg: qt on KDE distroes in the future, gtk2 on gnome). So if use installs lazarus they get dependency lazarus-lcl which in turn installs lazarus-lcl-whatever. This needs a bit more explaining. Here's a package list for a debian distro with dependencies in [], comments in () lazarus-common (provides basic stuff, non code/.ppu/.o) lazarus-source (obvious) lazarus-lcl-gtk1 [lazarus-common] (gtk1 specific LCL units/.ppu/.o) lazarus-lcl-gtk2 [lazarus-common, lazarus-lcl-gtk1?] (gtk2 specific LCL units/.ppu/.o) lazarus-lcl-qt4 [lazarus-common] (qt4 specific LCL units/.ppu/.o) lazarus-lcl [lazarus-lcl-specific_for_distro] (dummy package for people who don't know, and higher packages) lazarus-tools [lazarus-common, lazarus-lcl] (contains lazbuil and other stuff from tools subdir) lazarus-ide-gtk1 [lazarus-common, lazarus-lcl-gtk1, lazarus-source] (the ide itself, specific for gtk1) lazarus-ide-gtk2 [lazarus-common, lazarus-lcl-gtk2, lazarus-source] (the ide itself, specific for gtk2) lazarus-ide-qt4 [lazarus-common, lazarus-lcl-qt4, lazarus-source] (the ide itself, specific for gtk1) llazarus-ide [lazarus-common, lazarus-lcl, lazarus-source] (dummy for the ide itself) I'm not sure if lazarus-common would be needed at all, or needed by code packages (perhaps just by the IDE) Ales _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
[lazarus] Lazarus packaging
I wanted to ask about plans to support better packaging of lazarus and apps made by lazarus on Linux distros in the future. For reference I'll use .deb style here but I'm sure .rpm will have to be quite similar. 1. Does lazarus support root/readonly locations yet? (including support for installing components) This is crucial for everything really. 2. I think lazarus should get separated into lazarus-lcl-widgetset packages, lazarus-ide and lazarus-tools (lazbuild and friends) with a dummy all-package like lazarus and a dummy lcl package which will simply default to per-distro widgetset (eg: qt on KDE distroes in the future, gtk2 on gnome). So if use installs lazarus they get dependency lazarus-lcl which in turn installs lazarus-lcl-whatever. 3. With lazarus-tools, users can easily create lazarus/fpc-made packages for whatever they made. They will simply specify the dependency for lazarus-lcl-specific for binary packages and lazarus-lcl for -src packages and use lazarus-tools (lazbuild) to automate building. 3rd party components should be of-course packagable as well. I'm not asking for someone to do it, but for input, and if it's viewed as feasible by you guys. I'm currently about to release a LaTeX IDE I made with Lazarus and am quite.. blocked in regards to proper packaging and auto-building of the thing. So.. what do you think? Of course, fpc will have to be packaged properly as well, which means addition of the missing fpc-source debian package :D I'd also propose to add the fpc package to lazarus deb repository. Ales _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Lazarus packaging
On Thu, 31 Jan 2008 18:05:24 +0100 Ales Katona [EMAIL PROTECTED] wrote: I wanted to ask about plans to support better packaging of lazarus and apps made by lazarus on Linux distros in the future. For reference I'll use .deb style here but I'm sure .rpm will have to be quite similar. 1. Does lazarus support root/readonly locations yet? (including support for installing components) This is crucial for everything really. If you mean that the package sources are installed read only: yes 2. I think lazarus should get separated into lazarus-lcl-widgetset packages, lazarus-ide and lazarus-tools (lazbuild and friends) with a dummy all-package like lazarus and a dummy lcl package which will simply default to per-distro widgetset (eg: qt on KDE distroes in the future, gtk2 on gnome). So if use installs lazarus they get dependency lazarus-lcl which in turn installs lazarus-lcl-whatever. Possible. 3. With lazarus-tools, users can easily create lazarus/fpc-made packages for whatever they made. They will simply specify the dependency for lazarus-lcl-specific for binary packages and lazarus-lcl for -src packages and use lazarus-tools (lazbuild) to automate building. 3rd party components should be of-course packagable as well. Maybe improve fppackage instead? I'm not asking for someone to do it, but for input, and if it's viewed as feasible by you guys. I'm currently about to release a LaTeX IDE I made with Lazarus and am quite.. blocked in regards to proper packaging and auto-building of the thing. So.. what do you think? Of course, fpc will have to be packaged properly as well, which means addition of the missing fpc-source debian package :D Why missing? I'd also propose to add the fpc package to lazarus deb repository. Why? Mattias _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Lazarus packaging
Mattias Gaertner wrote / napísal(a): On Thu, 31 Jan 2008 18:05:24 +0100 Ales Katona [EMAIL PROTECTED] wrote: I wanted to ask about plans to support better packaging of lazarus and apps made by lazarus on Linux distros in the future. For reference I'll use .deb style here but I'm sure .rpm will have to be quite similar. 1. Does lazarus support root/readonly locations yet? (including support for installing components) This is crucial for everything really. If you mean that the package sources are installed read only: yes I mean that you install lazarus from a .deb into eg: /usr/lib/lazarus and that people can still install 3rd party components into this lazarus in some way (I realize that packaged components would conflict tho, because of the one binary problem, but that's a bit different beast) Maybe improve fppackage instead? I'm not sure if fppkg would be welcomed as build-tool/3rd party repository to enable -src package autobuilds. (actually I'm sure it wouldn't) Why missing? Because lazarus needs it for auto-completion. I'd also propose to add the fpc package to lazarus deb repository. Why? See above. Mattias Ales _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Lazarus packaging
Ales Katona schreef: 2. I think lazarus should get separated into lazarus-lcl-widgetset packages, lazarus-ide and lazarus-tools (lazbuild and friends) with a dummy all-package like lazarus and a dummy lcl package which will simply default to per-distro widgetset (eg: qt on KDE distroes in the future, gtk2 on gnome). So if use installs lazarus they get dependency lazarus-lcl which in turn installs lazarus-lcl-whatever. In which package will be forms.ppu? It is needed by lazarus-lcl-gtk2 and lazarus-lcl-qt and lazarus-lcl is just a dummy package. I think you need a lazarus-lcl-common too. (You may thing about better names) I'd also propose to add the fpc package to lazarus deb repository. Isn't this the case already? I see a lot of fpc debs here. http://www.hu.freepascal.org/lazarus/dists/lazarus-stable/universe/binary-i386/Packages Vincent _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Lazarus packaging
Vincent Snijders wrote / napísal(a): Ales Katona schreef: 2. I think lazarus should get separated into lazarus-lcl-widgetset packages, lazarus-ide and lazarus-tools (lazbuild and friends) with a dummy all-package like lazarus and a dummy lcl package which will simply default to per-distro widgetset (eg: qt on KDE distroes in the future, gtk2 on gnome). So if use installs lazarus they get dependency lazarus-lcl which in turn installs lazarus-lcl-whatever. In which package will be forms.ppu? It is needed by lazarus-lcl-gtk2 and lazarus-lcl-qt and lazarus-lcl is just a dummy package. I think you need a lazarus-lcl-common too. (You may thing about better names) Yes, lazarus-lcl-common sounds good for this purpose. (what's wrong with the names? they should be descriptive I think) I'd also propose to add the fpc package to lazarus deb repository. Isn't this the case already? I see a lot of fpc debs here. http://www.hu.freepascal.org/lazarus/dists/lazarus-stable/universe/binary-i386/Packages Didn't know this, but fpc still has the debs listed just like that in some ftp site. Perhaps we should unify this? eg: provide the repository for debianists on fpc page too. Vincent Ales _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
Re: [lazarus] Lazarus packaging
Ales Katona schreef: Vincent Snijders wrote / napísal(a): Ales Katona schreef: 2. I think lazarus should get separated into lazarus-lcl-widgetset packages, lazarus-ide and lazarus-tools (lazbuild and friends) with a dummy all-package like lazarus and a dummy lcl package which will simply default to per-distro widgetset (eg: qt on KDE distroes in the future, gtk2 on gnome). So if use installs lazarus they get dependency lazarus-lcl which in turn installs lazarus-lcl-whatever. In which package will be forms.ppu? It is needed by lazarus-lcl-gtk2 and lazarus-lcl-qt and lazarus-lcl is just a dummy package. I think you need a lazarus-lcl-common too. (You may thing about better names) Yes, lazarus-lcl-common sounds good for this purpose. (what's wrong with the names? they should be descriptive I think) For instance: lazarus-lcl-comom - just lazarus-lcl lazarus-lcl - lazarus-lcl-widgetset, lazarus-lcl-default-ws or lazarus-lcl-for-dummies ;-) Vincent _ To unsubscribe: mail [EMAIL PROTECTED] with unsubscribe as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
