Ticket #231 (closed defect: fixed)
Installation with cpan may create root owned files under .padre in users home dir
| Reported by: | puudeli | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | External dependency | Version: | 0.25 |
| Keywords: | installation permissions | Cc: |
Description
If Padre is installed using sudo'ed cpan, the installation process creates root:root owned .padre directory tin users home directory. This prevent starting Padre with the following error:
cpt2jmo@phantom:~$ padre cpt2jmo@phantom:~$ mkdir /home/cpt2jmo/.padre/plugins/cache: Permission denied at /usr/local/share/perl/5.8.8/Padre/PluginManager.pm line 337
When looking at .padre you can see the following:
cpt2jmo@phantom:~$ ls -la ~ ... drwxr-xr-x 3 root root 4096 2009-01-16 10:25 .padre ... cpt2jmo@phantom:~$ cd .padre/ cpt2jmo@phantom:~/.padre$ ls -al total 28 drwxr-xr-x 3 cpt2jmo cpt2jmo 4096 2009-01-16 10:25 . drwxr-xr-x 54 cpt2jmo cpt2jmo 4096 2009-01-16 10:25 .. -rw-r--r-- 1 root root 12288 2009-01-16 10:25 config.db -rw-r--r-- 1 root root 7 2009-01-16 10:25 config.yml drwxr-xr-x 3 root root 4096 2009-01-16 10:25 plugins
When these files (and .padre) are chown'ed back to the user Padre starts just fine.
Change History
Note: See
TracTickets for help on using
tickets.

During installation Padre should not mess with .padre at all!
Maybe this is a test that does not use a temporary home for Padre ?