On Sat, 05 Aug 2006 14:14:58 +0200, MJ Ray <[EMAIL PROTECTED]> wrote:
"Lucas C. Villa Real" <[EMAIL PROTECTED]>
On 8/1/06, MJ Ray <[EMAIL PROTECTED]> wrote:
> Sending recipes in a text-like format is good because:
> 1. it's easier for the gurus to read through quickly
> 2. we avoid the 33% base64 size penalty, and
> 3. people can cut-and-paste bits out of the archive later if needed.
Well, I don't really like it, to be sincere. It's much better to me to
review recipes in a tarball, since I already have a 'ReviewRecipes'
script which deals with that. RecipeLint also takes a tarball as a
parameter and inspects it in a transparent way.
Why do you find it better to review recipes in a tarball?
I've explained why MIME-attached tarballs are frustratingly bad.
How can you read them from your mail client?
I can give ou my view on why I wouldn't like your MailRecipe.
First of all, I couldn't create a recipe from the code you gave me.
Perhaps I did it the wrong way, so if you want to convince me, send me a
mail with a MailRecipe attachment and a clear description what to do.
Secondly, as I use a graphical mail client it was hard to copy-paste the
commands to the console. I'd much rather have a file that I save to disk.
Even though your format lets me read much of the recipe directly in the
email, I'd rather go for a tarball.
One of RecipeLint's early actions is to unpack the tarball, so it
could take a directory like the one produced by the MailRecipe
format without too much work. That's probably a good idea, as it
would let people check their local recipes before trying to
Compile them and failing.
Yes, one of the first things RecipeLint does is to unpack the recipe. Otoh
it does it automagically, so the user isn't aware of this unless he/she
reads the code of RecipeLint.
Just my €0.02
--
/Jonas
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
