[MTOS-dev] RPMs?

[David Jacobs]

(calling out Finn! Sorry Finn!)

Finn Smith developed a debian package for us last year that let people
choose their database at the time of install. I believe he's in the
process of releasing that. In the meantime, we should not create extra
work by fracturing the package. Two (or 1+$number_of_supported_
database) packages instead of one is harder, not easier.

On 1/9/08, Erik Ogan <erik at ogan.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Jan 2, 2008, at 8:09 AM, Bud Gibson wrote:
> > I suspect mysql is by far the database most people are running on.
> > I would almost say that should be the default.
>
> Please, I beg of you, a thousand times no. I worked hard to eradicate
> that half-baked, half-assed, (at best) half-reliable, steaming pile
> that passes for an RDBMS from our servers! (You might not be able to
> guess, but I feel somewhat passionately about this. Even though most
> of the ways MT uses Postgres it might as well be MySQL. ;)
>
> My suggestion would be to break the database engine code into
> separate packages  (I believe the design would make this separation
> easy: movabletype-mysql, movabletype-postgresql, movabletype-sqllite,
> etc.) all of which provide the virtual "movabletype-database"
> package, and have the movabletype pakckage require that. This would
> allow administrators to install only the engine(s) they care to support.
>
> Having said that, I suspect your statement is probably true, and that
> I'm one of the few exceptions that care about anything but MySQL, so
> I'll happily volunteer to do do that work. I was definitely going to
> make RPMS, but I was waiting for a stable, non-beta release before I
> started working on it. :)
>
> The only downside I can see to this scheme is that "Where do I find
> the 'movabletype-database' package?" could become an FAQ, or at least
> a point of confusion for newbies. The consolation to this is that if
> they're using Yum or RHEL's equvalent (which is yum-based these days
> anyway, isn't it?) I THINK it will suggest packages to fulfill the
> requirement. Which means we should probably set up a yum repository
> for MT, probably not a bad idea anyway, I'd be happy to do that, too,
> though it'd be better served from movabletype.org
>
>
> > Are you taking into account running on SELinux as one does with
> > RHEL5?  My read of the spec file suggests no.  SELinux required a
> > significant amount of configuring when I did it a few months ago.
> > I'm fixing to do it again.
>
> Ooh, this was something I'd not considered, either. Having written
> SELinux policies in my day job, I'd be happy to volunteer some help
> for this as well.
>
> - -e
>
>
> - --
> Erik R. Ogan                                    Mercenary Developer
> PGP Key:         http://erik.ogan.net/PGP.txt            0 o . _O-d
> PGP Fingerprint: A3DB 678A 4737 32E7 F703  DC3A 6BFE 2BBC 4F41 A371
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (Darwin)
>
> iD8DBQFHhOzBa/4rvE9Bo3ERAvoIAJ45MmzydEgslE/uHX6TIiBiPpQYqgCgkBUJ
> nIBTTZVTG912fJ7O5VzON8k=
> =WBQW
> -----END PGP SIGNATURE-----
> _______________________________________________
> MTOS-dev mailing list
> MTOS-dev at sixapart.com
> http://www.sixapart.com/mailman/listinfo/mtos-dev
>


-- 
David Jacobs
http://Apperceptive.com
917 450 0533