- Changelog file to live in
DEBIAN/changelog
.changelog
file can be added tomongosh
repo root.pkg-deb
can then copy it over to its internalDEBIAN
dir. Format should be as follows:
package (version) distribution(s); urgency=urgency
[optional blank line(s), stripped]
* change details
more change details
[blank line(s), included in output of dpkg-parsechangelog]
* even more change details
[optional blank line(s), stripped]
-- maintainer name <email address>[two spaces] date
- Package needs to be tested for Debian standards.
- Package needs to have a control file with essential information about the package, like version, maintainer, desciption.
- Maintainer field allows only for one maintainer. Use team as a maintainer.
- Description/ProductDescription needs to be adjusted to Debian standards.
- Update to a more eloquent description before sending to mentors.debian.net, so it'll be easier to find a sponsor.
- Package needs to have LICENSE files of all 3rd party packages being used. This might need to be generated in build by looking at all
package.json
in./packages
and extracting LICENSE files from all packages independencies
. - Package should have a readme.
pkg-deb
should copy overmongosh
readme from root intoDEBIAN/README
.
Instructions on Publishing a Package and adding it to mentors.debian.net.
Uploading to mentors.debian.net can be done via FTP, which means we can automate this process from our build.
Every package uploaded needs a mentor, or a sponsor, that is a member of the Debian Community who will verify and approve your package added to the Debian repository.
Verification of our package will have to happen with every patch release. That is, we are unable to be the ones uploading the pacakge, the sponsor uploads the package.