1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
|
5 |
On Jun 30, 2004, at 6:18 PM, Mike Frysinger wrote: |
6 |
|
7 |
> On Wednesday 30 June 2004 04:24 am, Brian Harring wrote: |
8 |
>> Anyone have a reason why we have files w/ +x set in the tree? |
9 |
>> Being paranoid/anal, but the bit isn't really needed. If executable |
10 |
>> is |
11 |
>> needed, set it when transferring the file out of ${FILESDIR} during |
12 |
>> the |
13 |
>> install stage. |
14 |
> |
15 |
> i think when the file should be executable, it should be stored with a |
16 |
> +x, but |
17 |
> otherwise it shouldnt ... |
18 |
|
19 |
All files being transfered out of filesdir that needs +x is quite |
20 |
likely being installed via newexe/doexe, which installs with the |
21 |
appropriate permissions already. |
22 |
Any ebuild *not* using newexe/doexe for installing binaries ought to be |
23 |
fixed, since assuming the permissions for files in the tree are correct |
24 |
isn't sane. |
25 |
So the actual permissions of the files in the tree don't matter :) |
26 |
|
27 |
> for example, every once in a while ebuilds/digests/metadatas/licenses |
28 |
> pop up |
29 |
> with +x on them and there's no real way to clear it short of |
30 |
> removing/adding |
31 |
> the file or having the cvs admin clear it |
32 |
|
33 |
http://bugs.gentoo.org/show_bug.cgi?id=55647 |
34 |
|
35 |
has a patch to make repoman check up on the permissions- ebuild's w/ +x |
36 |
are marked as failures, files w/ +x are marked as warnings. |
37 |
~brian |
38 |
-----BEGIN PGP SIGNATURE----- |
39 |
Version: GnuPG v1.2.4 (Darwin) |
40 |
|
41 |
iD8DBQFA42W0vdBxRoA3VU0RAqf3AKC480K3H4q+qAa1CHpcNncEhjUnHQCgtirY |
42 |
d3g9F77HcUNpVIYSf6O9zEE= |
43 |
=178l |
44 |
-----END PGP SIGNATURE----- |
45 |
|
46 |
|
47 |
-- |
48 |
gentoo-dev@g.o mailing list |