Compile all units with the Debian FPC package, build the MSEide + tools binaries. 3. Build the MSEide+MSEgui *.deb Packages, add a dependency from FPC package. ================= It's the current way - the problem is to propagate the updates of MSE* bunch to the distro in time. Once contact to the menthor is established a new FPC version is issued which means new rebuilding which means new contacting...
So it seems Debian/Ubuntu are not interested on MSEide+MSEgui packages. Does the same apply for FPC packages? ================== Frankly saying, yes, the same - maybe because the Pascal language seems to be a moveton in LINUX at the moment. Both MSE* & LAZARUS were stooped in the distro approx 2 years ago. But the things have been changing. As written before the MSEgui units can be compiled by the user project in user home directory. ================== This approach means that we should only distribute source packages otherwise we may be penaltied. Should be checked for allowance by the current rules. 2012/1/9, Martin Schreiber <mse00...@gmail.com>: > On Monday 09 January 2012 09.18:56 IvankoB for-mse wrote: >> Did you contact this people in order to synchronize FPC-MSEide+MSEgui >> debian package release cycles? >> =========== >> How to say... Well, from my experience, there's approx 3..5% >> probability of the response in reasonable time (all menthors are very >> busy people since each of them controls of many different packages and >> do this work thoroughly to achieve the appraised DEBIAN >> "quality-of-state"). > > So it seems Debian/Ubuntu are not interested on MSEide+MSEgui packages. > Does > the same apply for FPC packages? > >> Anyway , the need in exact unit version match >> makes the thing much-much harder otherwise the whole MSE* packages >> bunch will be self-maintainable. >> > I don't see the problem. > 1. Install the Debian FPC package on your Debian system. > 2. Compile all units with the Debian FPC package, build the MSEide + tools > binaries. > 3. Build the MSEide+MSEgui *.deb Packages, add a dependency from FPC > package. > >> binaries are independent from FPC version >> ============= >> The problems is that the MSEgui units must match the FPC ones exactly >> otherwise MSEgui apps can't be built. >> > As written before the MSEgui units can be compiled by the user project in > user > home directory. > > Martin > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > mseide-msegui-talk mailing list > mseide-msegui-talk@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk > ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
