No self-respecting Archer will install an app without a PKGBUILD. Any plans to package it and upload to the AUR? Graysky 19:48, 28 November 2011 (EST)
- We could make a preconfigured glftpd and package that, but that would compromise so much of glftpd's security. This shouldn't be too hard, everything required to make a :preconfigured glftpd is there, but we would have to make choises for the user like:
- install to jail by default or not?
- install with encryption support by default or not?
- A user would also have to do a few things after a PKGBUILD installation:
- edit xinetd settings
- edit tcp_wrappers settings
- edit rc.conf
- edit his user's groups
- All this is handled by the install.sh script, do we want to take away the user's choise and prepackage that? --stefanwilkens 10:43, 28 December 2011 (EST)
- @stefan - I think these assumptions are good: jail by default; with encryption. If you are really concerned, you could make a variable to set in the PKGBULD itself for jail or no jail. See the PKGBUILD for AUR for an example.
- The final steps you describe are perfectly acceptable to have the user do after installation. Just document them (as them are) on the wiki page and give a post.install message directing the user to do so.
- Graysky 15:04, 28 December 2011 (EST)
- @Graysky - fair enough, you've convinced me that a PKGBUILD has merit. Most of the required actions are described in the install.sh anyway, I suppose I could just assume answers and use the methods in the installation script.--stefanwilkens 11:04, 29 December 2011 (EST)
- @stefan - It's a little bit of work to transpose an install.sh to a PKGBUILD but you'll find that very few if any Archer will run an install.sh on their systems. Pacman is the cornerstone of the distro ;)
- Graysky 07:56, 30 December 2011 (EST)