At 1:30 Uhr -0800 19.01.2002, Daniel Parks wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>On Friday, January 18, 2002, at 07:06  PM, Kyle Moffett wrote:
>
>><package name="foo" version="1.0.1" revision="2">
>
>Why name="foo", etc, but no maintainer="John Doe <[EMAIL PROTECTED]>"?

Well, as you realize, this was more a proof-of-concept 
implementation, to show that it can be done easily.

Personally I think (see my other maiL) that the maintainer field 
should be split. I also don't think it should be an attribute to the 
package element. Name, version and revision are direct (required) 
properties of every package; maintainer is not (well, it is required, 
but not a direct proprty of the package; it merely contains 
information, but is not esssential for the build/install process, nor 
for dpkg).


>>      <depends>bar, x11</depends>
>
>That comma syntax seems a bit un-XML.

Yup, should be a list of <depends> elements instead. But again to 
defend Kyle, I think this was meant as a proof of concept only :)


>
>>      <maintainer><![CDATA[John Doe <[EMAIL PROTECTED]>]]></maintainer>
>
>Ugh. Time to learn XML "for real."

Huh, what?  I don't like doing it like that, but I's perfectly legal. 
The < and > appearing in the data have to be marked as CDATA. 
otherwise the file would be invalid XML. An alternative would be to 
translate them to &gt; and &lt; but I think that would be a really 
bad idea. So I think your remark is not very fitting.
In any case, for my opinion on this, see above/my other mail.



>
>></package>
>>
>>diffs will be posted on the feature request tracker shortly.
>
>I wanna subscribe to the trackers! Stupid SourceForge! :-(

Sorry, fink-tracker is right now only available for fink team memebers.


Max
-- 
-----------------------------------------------
Max Horn
Software Developer

email: <mailto:[EMAIL PROTECTED]>
phone: (+49) 6151-494890

_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to