Ciaran McCreesh wrote: > > Having to write an ebuild just to install something in a package manager > friendly way and be able to uninstall it cleanly later is a defect
No, this is exactly what ebuilds meant for: That the package manager keeps track of your package, and possibly also recompiles it in case of library upgrades. For this reason, ebuilds should essentially just consist of the commands which you would also type in the shell - this information *must* be provided (together with obviously some data like package name, slot-requests, and an otional description), but essentially that should be it. If it is more work or requires more knowledge to write an ebuild, then it is the ebuild concept which is defect.
