Ian Malone ibmalone@gmail.com writes:
There is no-one on the planet who thinks emacs is minimalistic
I`m not so sure about that. There are even ppl who have never heard about emacs, and if they`d see it, they might very well think it is.
With this and all your other examples you are talking about individual pieces of software. But what I mean is you've said you want specific things on the system that are not what other people would want and things they want are not what you want. On the Venn diagram of what's included in an install that makes life difficult.
Each user has preferences. It is not too difficult to give them choices. What I want to have installed is different from what someone else wants to have installed --- but we don`t get to pick before the installation is already done.
wasn`t anything better. There still isn`t --- and the LaTeX sources from back then can still be worked with and printed with no problem. I still have them.
Provided they only use packages that are compatible with the TeX distro you've got available.
Even if they don`t, I can still edit them and make adjustments if necessary. If anything fails, I can print the sources as they are. Had I used some WYSIWYG word processing software instead, I wouldn`t even be able to read them anymore because this word processing software doesn`t exist anymore since a long time.
I don`t know what would be better than packages. I wish there were more packages and am only saying it`s too difficult to make them. Perhaps there`s good reason for it, perhaps it can be made easier. Someone who knows how to make them might be able to tell.
Ultimately writing a basic spec file is pretty simple, if you can do the configure-make-install cycle it should be straightforward enough.
Is there some documentation about how one would make a package that can be integrated into Fedora?
How would I find out what the package would have to depend on?