Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

Am Samstag, 25. April 2009 16:29:03 schrieb Giovanni Scafora: > ln -s /srv/http/cgi-bin/htsearch ${pkgdir}/usr/bin || return 1 I thnik it should be the other way round. Imho no package should install anything into /srv. What do you guys think about this? -- Pierre Schmitz Clemens-August-Str

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

2009/4/25, Pierre Schmitz : > I thnik it should be the other way round. Imho no package should install > anything into /srv. > > What do you guys think about this? I think that is right. Moreover, there are documentation files in /srv/http/htdocs/ -- Arch Linux Developer (voidnull) AUR & Pac

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

Pierre Schmitz wrote: Am Samstag, 25. April 2009 16:29:03 schrieb Giovanni Scafora: ln -s /srv/http/cgi-bin/htsearch ${pkgdir}/usr/bin || return 1 I thnik it should be the other way round. Imho no package should install anything into /srv. What do you guys think about this? FHS

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

On Sat, Apr 25, 2009 at 10:31 AM, Allan McRae wrote: > Pierre Schmitz wrote: >> >> Am Samstag, 25. April 2009 16:29:03 schrieb Giovanni Scafora: >> >>> >>> ln -s /srv/http/cgi-bin/htsearch ${pkgdir}/usr/bin || return 1 >>> >> >> I thnik it should be the other way round. Imho no package should inst

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

> Installing into /srv/ is no different than installing into /home/, > IMO. It might be worse as it presents a relatively big security risk > for those that do run public facing services, and suddenly a new > script has been made available for web site users to run. if you think so I could change

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

2009/4/25, Dan McGee : > Installing into /srv/ is no different than installing into /home/, > IMO. It might be worse as it presents a relatively big security risk > for those that do run public facing services, and suddenly a new > script has been made available for web site users to run. Then,

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

On Sat, Apr 25, 2009 at 10:45 AM, Giovanni Scafora wrote: > 2009/4/25, Dan McGee : >> Installing into /srv/ is no different than installing into /home/, >>  IMO. It might be worse as it presents a relatively big security risk >>  for those that do run public facing services, and suddenly a new >>

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

On 25/04/2009, Dan McGee wrote: > I would just say/think that files in /srv/ should be managed by the > system admin and not pacman- anything they want in there should be > linked by the sysadmin from /usr/bin/ or elsewhere, rather than the > other way around. You are right. so voidnull is fixing

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

2009/4/25, Andrea Scarpino : > You are right. > so voidnull is fixing this soon, because I'm not in my home. Fixed. -- Arch Linux Developer (voidnull) AUR & Pacman Italian Translations Microdia Developer http://www.archlinux.it

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

Am Samstag, 25. April 2009 17:36:19 schrieb Dan McGee: > Installing into srv is no different than installing into /home/, > IMO. It might be worse as it presents a relatively big security risk > for those that do run public facing services, and suddenly a new > script has been made available for we

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)

Pierre Schmitz schrieb: Am Samstag, 25. April 2009 16:29:03 schrieb Giovanni Scafora: ln -s /srv/http/cgi-bin/htsearch ${pkgdir}/usr/bin || return 1 I thnik it should be the other way round. Imho no package should install anything into /srv. What do you guys think about this? There should