Emiliano wrote:
>
> Alexander Bokovoy wrote:
>
> > I'd rather suggest to not distribute Midgard-lib as alone RPM but use our
> > latest Midgard.spec which builds RPM with whole Midgard as one (two - for
> > Midgard-devel part) package. This way all things are in sync. We created a set
> > of RPMs for RH 6.2 and Mandrake 7.2 during yesterday and this night and I hope
> > they will be published soon as a part of demo CD for Brussells' Linux Forum.
>
> I prefer the separate packages. Leaner upgrades (there's no need to
> download all of PHP when something gets fixed in lib) and when PHP4
> arrives there's no need to put mo, lib, php and php4 in one package.
Before final release I prefer to do monilitic package (or two -- one with
program, second with data) because we are extending lowlevel API sometimes and
even functionality -- like with Repligard integration. The closest change will
be with iconv support at midgard-lib API level, not inside Repligard because
several other features (FT, for example) should use it too. Another point
because it is better to provide monolitic 1.4 RPMs is from dstribution side:
always better to put really monolitic program into one-two RPMs (second -- for
data or even third for development libraries like in RedHat on Mandrake
package building policy). As soon as Midgard will support several languages or
PHP3/PHP4 in the same time, this can be changed. But from philosofical point
of view, it's better to not multiply creatures.
--
Sincerely yours, Alexander Bokovoy
The Midgard Project | www.midgard-project.org | Aurora R&D team
Minsk Linux Users Group | www.minsk-lug.net | www.aurora-linux.com
IPLabs Linux Team | linux.iplabs.ru | Architecte Open Source
-- We want to create puppets that pull their own strings.
- Ann Marion
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
