Skip to main content
added 83 characters in body
Source Link
muru
  • 78.1k
  • 16
  • 213
  • 319

If you're making a package, it does depend somewhat on the distro you're targeting. You can follow the Filesystem Hierarchy Standard. Debian follows FHS, with some exceptions. Essentially:

  • /etc: Host-specific system configuration
  • /usr/bin: Most user commands
  • /usr/lib: Libraries for programming and packages
  • /usr/share: Architecture-independent data

On Debian-based systems for packages that support multiple architectures, the architecture-independent data is often split off into a separate package.

See, for example, how apache2, apache2-bin and and, apache2-data and apache2-doc packages on Ubuntu are organised.

If you're making a package, it does depend somewhat on the distro you're targeting. You can follow the Filesystem Hierarchy Standard. Debian follows FHS, with some exceptions. Essentially:

  • /etc: Host-specific system configuration
  • /usr/bin: Most user commands
  • /usr/lib: Libraries for programming and packages
  • /usr/share: Architecture-independent data

On Debian-based systems for packages that support multiple architectures, the architecture-independent data is often split off into a separate package.

See, for example, how apache2, apache2-bin and and apache2-data packages on Ubuntu are organised.

If you're making a package, it does depend somewhat on the distro you're targeting. You can follow the Filesystem Hierarchy Standard. Debian follows FHS, with some exceptions. Essentially:

  • /etc: Host-specific system configuration
  • /usr/bin: Most user commands
  • /usr/lib: Libraries for programming and packages
  • /usr/share: Architecture-independent data

On Debian-based systems for packages that support multiple architectures, the architecture-independent data is often split off into a separate package.

See, for example, how apache2, apache2-bin, apache2-data and apache2-doc packages on Ubuntu are organised.

added 26 characters in body
Source Link
muru
  • 78.1k
  • 16
  • 213
  • 319

ThisIf you're making a package, it does depend somewhat on the distro you're targeting. You can follow the Filesystem Hierarchy Standard. Debian follows FHS, with some exceptions. Essentially:

  • /etc: Host-specific system configuration
  • /usr/bin: Most user commands
  • /usr/lib: Libraries for programming and packages
  • /usr/share: Architecture-independent data

On Debian-based systems for packages that support multiple architectures, the architecture-independent data is often split off into a separate package.

See, for example, how apache2, apache2-bin and and apache2-data packages on Ubuntu are organised.

This does depend somewhat on the distro you're targeting. You can follow the Filesystem Hierarchy Standard. Debian follows FHS, with some exceptions. Essentially:

  • /etc: Host-specific system configuration
  • /usr/bin: Most user commands
  • /usr/lib: Libraries for programming and packages
  • /usr/share: Architecture-independent data

On Debian-based systems for packages that support multiple architectures, the architecture-independent data is often split off into a separate package.

See, for example, how apache2, apache2-bin and and apache2-data packages on Ubuntu are organised.

If you're making a package, it does depend somewhat on the distro you're targeting. You can follow the Filesystem Hierarchy Standard. Debian follows FHS, with some exceptions. Essentially:

  • /etc: Host-specific system configuration
  • /usr/bin: Most user commands
  • /usr/lib: Libraries for programming and packages
  • /usr/share: Architecture-independent data

On Debian-based systems for packages that support multiple architectures, the architecture-independent data is often split off into a separate package.

See, for example, how apache2, apache2-bin and and apache2-data packages on Ubuntu are organised.

Source Link
muru
  • 78.1k
  • 16
  • 213
  • 319

This does depend somewhat on the distro you're targeting. You can follow the Filesystem Hierarchy Standard. Debian follows FHS, with some exceptions. Essentially:

  • /etc: Host-specific system configuration
  • /usr/bin: Most user commands
  • /usr/lib: Libraries for programming and packages
  • /usr/share: Architecture-independent data

On Debian-based systems for packages that support multiple architectures, the architecture-independent data is often split off into a separate package.

See, for example, how apache2, apache2-bin and and apache2-data packages on Ubuntu are organised.