Re: ebuilds in XML
"Kevin Horn" <[email protected]> Sun, 29 Jun 2003 19:04:34 -0500
| Newsgroups | gmane.linux.zynot.general |
|---|---|
| Message-ID | <021e01c33e9b$30e93a30$0301a8c0@maxilius> |
This is a multi-part message in MIME format. --===============4850201354953767== Content-Type: multipart/alternative; boundary="----=_NextPart_000_021B_01C33E71.47605CF0" This is a multi-part message in MIME format. ------=_NextPart_000_021B_01C33E71.47605CF0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable very spiffy! Obviously just a prototype, but it demonstrates your idea = very nicely. Using a system like this, one could store the metadata = portion of an ebuild as XML, have the actual install script = auto-generated, and thereby avoid having to rewrite a lot of common = tasks in bash (or whatever shell language). The XSLT could rapidly = become non-trivial, but I think this is a great direction to explore. Hmmm...could a particular package have one XML file, and a number of = different XSLT templates for different platforms? i.e. one XML file per package, and one XSLT file per platform, all = packages use the same XSLT transform for a particular platform? Hmmm, also, perhaps one might need several "layers" of XSLT transform... XML + XSLT1 -> XML2 XML2 + XSLT -> Bash? install script I'm not even sure why you would do this, but it could come in handy? = maybe? Ooooh! This approach would also be useful for autogenerating certain = docs or parts of docs. =20 e.g. Package description on website auto-generates details on deps, = available USE flags, etc. The more I think about this, the more I like it. =20 Anyone wanna play devil's advocate? ----- Original Message -----=20 From: Benjamin Judas=20 To: [email protected]=20 Sent: Saturday, June 28, 2003 5:11 PM Subject: [Zynot-pkgmgr] ebuilds in XML -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here is my idea of the ebuilds in XML: I am thinking of an ebuild completely written in XML. When "emerging" a special xslt is applied to the XML-file which = translates the=20 XML-file into a regular shell-script which then is executed. Pleas see the attachments. I know, they aren't very impressive - it's = just an=20 example, how to translate them into a shell-script. Take this as an impressive idea. regards, Benjamin "beejay" Judas P.S. : I call the ebuilds "receipts" since they are receipts how to = compile=20 and install a package - --=20 Benjamin Judas Schlo=DFgasse 51 35325 M=FCcke GERMANY Public-Key: http://blackhole.pca.dfn.de:11371/pks/lookup?op ICQ: 239829549 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+/hKx4BeHt8Md7dgRAm6oAJ4/ghRKVbYTNTRfFf/wRyc1DNTlJACfXiWb gszJanIOK5Qhz2Tqd1ZTTeo=3D =3D5vQo -----END PGP SIGNATURE----- -------------------------------------------------------------------------= ----- _______________________________________________ Zynot-pkgmgr mailing list [email protected] http://lists.zynot.org/mailman/listinfo/zynot-pkgmgr ------=_NextPart_000_021B_01C33E71.47605CF0 Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Diso-8859-15" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>very spiffy! Obviously just a = prototype, but=20 it demonstrates your idea very nicely. Using a system like this, = one could=20 store the metadata portion of an ebuild as XML, have the actual install = script=20 auto-generated, and thereby avoid having to rewrite a lot of common = tasks in=20 bash (or whatever shell language). The XSLT could rapidly become=20 non-trivial, but I think this is a great direction to = explore.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Hmmm...could a particular package have = one XML=20 file, and a number of different XSLT templates for different=20 platforms?</FONT></DIV> <DIV><FONT face=3DArial size=3D2>i.e. one XML file per package, and one = XSLT file=20 per platform, all packages use the same XSLT transform for a particular=20 platform?</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Hmmm, also, perhaps one might need = several "layers"=20 of XSLT transform...</FONT></DIV> <DIV><FONT face=3DArial size=3D2>XML + XSLT1 -> XML2</FONT></DIV> <DIV><FONT face=3DArial size=3D2>XML2 + XSLT -> Bash? install = script</FONT></DIV> <DIV><FONT face=3DArial size=3D2>I'm not even sure why you would do = this, but it=20 could come in handy? maybe?</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>Ooooh! This approach would also = be useful for=20 autogenerating certain docs or parts of docs. </FONT></DIV> <DIV><FONT face=3DArial size=3D2>e.g. Package description on website = auto-generates=20 details on deps, available USE flags, etc.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=3DArial size=3D2>The more I think about this, the more I = like=20 it. </FONT></DIV> <DIV><FONT face=3DArial size=3D2>Anyone wanna play devil's = advocate?</FONT></DIV> <BLOCKQUOTE=20 style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: = 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px"> <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV> <DIV=20 style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: = black"><B>From:</B>=20 <A href=3D"mailto:[email protected]" = [email protected]>Benjamin=20 Judas</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20 href=3D"mailto:[email protected]"=20 [email protected]>[email protected]</A> = </DIV> <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, June 28, 2003 = 5:11=20 PM</DIV> <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Zynot-pkgmgr] ebuilds = in=20 XML</DIV> <DIV><BR></DIV>-----BEGIN PGP SIGNED MESSAGE-----<BR>Hash: = SHA1<BR><BR>Here is=20 my idea of the ebuilds in XML:<BR><BR>I am thinking of an ebuild = completely=20 written in XML.<BR><BR>When "emerging" a special xslt is applied to = the=20 XML-file which translates the <BR>XML-file into a regular shell-script = which=20 then is executed.<BR><BR>Pleas see the attachments. I know, they = aren't very=20 impressive - it's just an <BR>example, how to translate them into a=20 shell-script.<BR><BR>Take this as an impressive=20 idea.<BR><BR>regards,<BR>Benjamin "beejay" Judas<BR><BR>P.S. : I call = the=20 ebuilds "receipts" since they are receipts how to compile <BR>and = install a=20 package<BR>- -- <BR><BR>Benjamin Judas<BR>Schlo=DFgasse = 51<BR><BR>35325=20 = M=FCcke<BR>GERMANY<BR><BR>Public-Key:<BR>http://blackhole.pca.dfn.de:1137= 1/pks/lookup?op<BR><BR>ICQ:=20 239829549<BR><BR><BR>-----BEGIN PGP SIGNATURE-----<BR>Version: GnuPG = v1.2.2=20 = (GNU/Linux)<BR><BR>iD8DBQE+/hKx4BeHt8Md7dgRAm6oAJ4/ghRKVbYTNTRfFf/wRyc1DN= TlJACfXiWb<BR>gszJanIOK5Qhz2Tqd1ZTTeo=3D<BR>=3D5vQo<BR>-----END=20 PGP SIGNATURE-----<BR> <P> <HR> <P></P>_______________________________________________<BR>Zynot-pkgmgr = mailing=20 = list<BR>[email protected]<BR>http://lists.zynot.org/mailman/li= stinfo/zynot-pkgmgr<BR></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_021B_01C33E71.47605CF0-- --===============4850201354953767== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Zynot-pkgmgr mailing list [email protected] http://lists.zynot.org/mailman/listinfo/zynot-pkgmgr --===============4850201354953767==--