1 |
2011/4/4 Tomáš Chvátal <scarabeus@g.o>: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> Dne 4.4.2011 01:13, Arfrever Frehtes Taifersar Arahesis napsal(a): |
6 |
>> 2011-04-03 21:28:02 Tomáš Chvátal napisał(a): |
7 |
>>> Dne 3.4.2011 19:38, Arfrever Frehtes Taifersar Arahesis napsal(a): |
8 |
>>>> I would like to add python-namespaces.eclass. This eclass will be used by a small number of |
9 |
>>>> special packages, which will provide Python namespaces. These packages will be used as |
10 |
>>>> dependencies of other packages already present in the tree. |
11 |
>>>> |
12 |
>>>> Ebuilds using this eclass must set PYTHON_NAMESPACES variable before inheriting this eclass. |
13 |
>>>> Example (from net-zope/namespaces-zope): |
14 |
>>>> PYTHON_NAMESPACES="Products Shared Shared.DC five +zope zope.app" |
15 |
>>>> |
16 |
>>>> This eclass provides 3 public functions: |
17 |
>>>> python-namespaces_src_install() |
18 |
>>>> python-namespaces_pkg_postinst() |
19 |
>>>> python-namespaces_pkg_postrm() |
20 |
>>>> |
21 |
>>> Why you do so much overquoting in the conditions? |
22 |
>> |
23 |
>> I like consistency with python.eclass and improved syntax highlighting :) . |
24 |
> Improved syntax highlighting? Apart from making it a bit larger that |
25 |
> indeed is not a point if bash has to process and strip all the quotes |
26 |
> your code is to be slower than the one without them. |
27 |
|
28 |
If you are going to complain about quotes, at least complain sanely. |
29 |
The cost of 'parsing the quotes' is negligible. It is not a question |
30 |
of performance, it is a question of readability and style. |
31 |
|
32 |
>> |
33 |
>>> Why do you die on those arguments, just ignore them... |
34 |
>> |
35 |
>> The policy for Python-related eclasses is to not ignore misusage of functions. |
36 |
> |
37 |
> It is policy defined by you that makes the code larger for no gain. You |
38 |
> do the same when you check if the ebuild scope is the same for the |
39 |
> function. These checks are not required for any aparent reason. If |
40 |
> developer wants to execute src_unpack in src_prepare and shoot himself |
41 |
> into his leg eclasses are not the one that should prevent him from doing |
42 |
> so. Basically you just add useless logic into the functions, so please |
43 |
> do not do that. (this apply for all your patches) |
44 |
>> |
45 |
>>> You could use some eclass-debug calls (see other eclasses) :) |
46 |
>> |
47 |
>> IMHO they are helpless in debugging. 'set -x' enabled by -d option of emerge is more helpful. |
48 |
>> |
49 |
> Ok if you don't feel it helps the development then indeed it is not |
50 |
> required to set them :) |
51 |
> |
52 |
>>> Why do you call those set_metadata right after its creation and delete |
53 |
>>> it right away, does it save so much time it is better than doing it in |
54 |
>>> global scope? |
55 |
>> |
56 |
>> It is used to have appropriate scope for local variables, so that they don't have to be unset |
57 |
>> manually immediately after the code, in which they should exist. |
58 |
>> |
59 |
> OOk works for me. |
60 |
> -----BEGIN PGP SIGNATURE----- |
61 |
> Version: GnuPG v2.0.17 (GNU/Linux) |
62 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
63 |
> |
64 |
> iEYEARECAAYFAk2Zl7wACgkQHB6c3gNBRYeH9wCfcac24FDG2t8Z1JFZbZ8AQDSv |
65 |
> Oq0An3AIfm+JehVVhZksgxmwNfhWi0Sd |
66 |
> =0qyh |
67 |
> -----END PGP SIGNATURE----- |
68 |
> |
69 |
> |