Here is a paper on how to make UNIX not suck:
http://www.helixcode.com/~miguel/bongo-bong.html
One of the sections is on code reuse. If you read the mpkg spec, you probably noticed the part about mpkg using Yozilla's rendering engine. I'm guessing that is code reuse. It makes sense: mpkg will need to parse XML meta-data. So, instead of re-inventing the proverbial wheel, why not use an existing one? Sure, it introduces a dependeny, but with the way mpkg handles packages, it's no problem(don't need yozilla, but want to keep mpkg? rpm wouldn't let you do it. But mpkg will unistall everything except for the rendering engine...because both packages "own" it).
Of course, I'm going to need loads of help on the spec. Especially on the command reference. And, can anybody give me there opinion on the package database? can anyone understand the basic concept? Does the database sound good? Does anybody not like it/wants to have it a different way? Of cours, nothing in the spec is set in stone. Just post your changes ot the club(or the mailing list).
I still need help on creating the DTDs for mpkg, the installer, app config(mentalUNIX apps will have XMl configuration files, therfore, we need DTDs for configuration), and the mpkg/installer display stuff(kinda like XHTML, but for mpkg)
---------------------------------------------
DO NOT REPLY TO THIS MESSAGE BY EMAIL!
---------------------------------------------
You have chosen to receive messages from "mentalunix" by email.
Reply to this message:
http://clubs.yahoo.com/clubs/mentalunix/bbsfrp?action=r&tid=mentalunix&sid=1600006580&mid=307
Unsubscribe from the Club mailing list:
http://clubs.yahoo.com/clubs/mentalunix/config/change_mb_list
Return to "mentalunix":
http://clubs.yahoo.com/clubs/mentalunix
----------------------------------------------
Not a member? Remove yourself from this list:
http://edit.clubs.yahoo.com/config/unsubscribe_mb_list?.userID=munix_devr&.groupID=mentalunix&.groupType=&.code=IVyJGMuRxG
|
