On Thu, Mar 31, 2011 at 1:56 PM, Andrea Scarpino andrea@archlinux.org wrote:
About FS#18157, many of them have been fixed (mysql, mpd, httpd...), but we need a complete list.
I guess the list can be generated by grepping all the PKGBUILDs for writes to /var/run and /var/lock.
Maybe it would be worth adding a warning to makepkg if files are written to /var/run, /var/lock, /tmp or /run?
Cheers,
Tom
On 31/03/11 22:15, Tom Gundersen wrote:
On Thu, Mar 31, 2011 at 1:56 PM, Andrea Scarpinoandrea@archlinux.org wrote:
About FS#18157, many of them have been fixed (mysql, mpd, httpd...), but we need a complete list.
I guess the list can be generated by grepping all the PKGBUILDs for writes to /var/run and /var/lock.
Maybe it would be worth adding a warning to makepkg if files are written to /var/run, /var/lock, /tmp or /run?
This is a check that can be added to namcap (not makepkg) once this gets implemented.
Allan
On 2011/3/31 Allan McRae allan@archlinux.org wrote:
On 31/03/11 22:15, Tom Gundersen wrote:
I guess the list can be generated by grepping all the PKGBUILDs for writes to /var/run and /var/lock.
Maybe it would be worth adding a warning to makepkg if files are written to /var/run, /var/lock, /tmp or /run?
This is a check that can be added to namcap (not makepkg) once this gets implemented.
I've created a feature request on Flyspray (FS#23539). Feel free to edit the description so that we remember all the reasons for the creation of this rule.
I have created it in the "Internal Dev" project because it seemed more appropriate. Is it ?
Rémy.
On Thu, Mar 31, 2011 at 1:52 PM, Rémy Oudompheng remyoudompheng@gmail.com wrote:
On 2011/3/31 Allan McRae allan@archlinux.org wrote:
On 31/03/11 22:15, Tom Gundersen wrote:
I guess the list can be generated by grepping all the PKGBUILDs for writes to /var/run and /var/lock.
Maybe it would be worth adding a warning to makepkg if files are written to /var/run, /var/lock, /tmp or /run?
This is a check that can be added to namcap (not makepkg) once this gets implemented.
I've created a feature request on Flyspray (FS#23539). Feel free to edit the description so that we remember all the reasons for the creation of this rule.
I have created it in the "Internal Dev" project because it seemed more appropriate. Is it ?
Only devs can view bugs in the "Internal Dev" project. So it would probably be better in the "Arch Linux" project.
Rémy.
arch-projects@lists.archlinux.org