05. Packages. Repository. Community

Distribution

A suit of components, set up for install, use and maintain software solution

Tasks:

• Inner half
  • Development
  • Integration
• Outer half
  • Delivery
  • Deployment
  • Maintaining

Historical stages of OS distribution:

0. Sowtware = hardware
1. Portable/upgradeable software
   • ⇒ need to deliver
   • ⇒ need to install/upgrade
2. Free/redistributable license

   • ⇒ legal full OS suit distribution

   • ⇒ need more infrastructure
3. Internet connectivity
   • ⇒ collaborative development

   • ⇒ modular software (packages)

   • ⇒ «rolling» updates and repository
4. Wast user community / clouds
   • ⇒ Application as distribution

   • (back to square one )

Free Licensing

To be debated later — need more time.

In short:

• Free_software is legal

• It is licensed

• People who receive a copy of the free software have the following four freedoms

  0. The freedom to run the program for any purpose.

  1. The freedom to study how the program works, and change it.

  2. The freedom to redistribute and make copies.

  3. The freedom to improve the program, and redistribute improved versions.

• Additionally, the Copyleft-aware license restricts further licensing to this:

  4. The same rights are to be preserved in derivative works

Distributions and community

Repository: a storage location for software packages.

• Legal to collect, update, integrate and distribute from
• Allows community-wide technology/resources
• Defines distribution workflow conventions

  • What is package

  • What is formal repository

  • How to downloand/install/upgrade packages from repo
  • How to check integrity of packages installed

Community tasks:

• Maintain repository
• Maintain individual packages in the repository
• Improve community-wide technology
• Maintain social/informational network

To be debated later — need more time.

Package

TODO https://uneex.ru/LecturesCMC/Distro2016/06_LinuxPackages

Other

TODO

• AppImage, Snap, Flatpak, 0Install, ...