Horizon/Packaging
< Horizon
Packaging
Packaging can easily be understood as: you're an engineer building a car. Unfortunately, you don't have anything else, other than a manual and very few tools. Any specific tool you'll require to actually build your car have to be created, too.
As example, if you you're going to add a library named "foo", it has to be
- Free Software
- all tools required to build it, have to be provided (as package) as well
- it has to be maintained, i.e. there needs to be an upstream
- it should NOT require a specific file system layout, FHS applies
It is not acceptable to purely copy code from other repositories into horizon source code. This tends to become a fork, diverging from its real upstream. The main reason for this is, it's not being maintained, and if a bug is discovered in original upstream, if can't easily be fixed by updating just a single package.
