--Sig_/7Vyrq2Py0104nGE+ywtB9Me Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sat, 22 Sep 2012 10:05:41 -0700 Brian Dolbec wrote: > On Sat, 2012-09-22 at 09:55 +0200, Micha=C5=82 G=C3=B3rny wrote: > > Hello, > >=20 > > The current dependency syntax: > >=20 > > [VERSION-OP] PACKAGE-NAME ["-" PACKAGE-VERSION] > >=20 > > suffers a few problems: > >=20 > >=20 > > 1. It is not really human-friendly. > >=20 > > People don't say things like: > >=20 > > I need newer than monkey-1.2. > >=20 > > They say instead: > >=20 > > I need monkey, newer than version 1.2. > >=20 > [snip :/ ] >=20 > > 4. It follows the syntax used by bash (for conditionals), pkg-config > > -- it is more natural in the environment. > >=20 >=20 > The BIG problem with that is bash has nothing to do with evaluating > dependencies. All bash does is source the *DEPEND and pass the value > to the package manager which does all the processing. And all 3 > current package managers are set up to parse those dep strings with a > set syntax and whitespace. None of the PM's dependency resolvers are > written in bash, two are python based, one C++. This proposal would > throw a big monkey wrench into parsing those strings. Introducing > lots of bugs, both in the PM and the ebuilds. It has all to do with people writing ebuilds. Also, I don't really see a problem with parsing it. Bash is not really relevant here; Python and C++ doesn't have a problem with either syntax. It's just about correct tokenizer design. > And this after all the fuss about the unified DEPENDENCIES proposal, > which is a small syntax change for the current processing code, easily > incorporated into the PM's. Err, no, it isn't. It requires redesigning ebuilds, cache, and probably a lot of code paths in the dependency parser unless the new syntax is going to be converted back to old one. Mine is easily incorporated into the PM; it is just a change in a single place splitting and parsing the tokens. > AND has definite, measurable advantages.=20 We still didn't get a single one. So, I think you just don't like it and are inventing disadvantages without even caring enough to consider them before writing. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/7Vyrq2Py0104nGE+ywtB9Me Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlBd8w0ACgkQfXuS5UK5QB16IgQAgYw8qxn18S+lDUZsrYLmsR4x b9d/Ef6xnZcBTDGSmwgBMD1/ZWVgDETrutnjvZNqqg6bYd6rqQV/cRNWbjKtTcYE zE9zScTXi+vHT7ONR2ZrzeiUA2QPubNG7lFalVEMHIY4eqPSETixB/G8NbhrBW4A mRQa03kVc4szImFt2CU= =9osu -----END PGP SIGNATURE----- --Sig_/7Vyrq2Py0104nGE+ywtB9Me--