Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provided Debian Packaging files #108

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gri6507
Copy link

@gri6507 gri6507 commented Sep 6, 2022

PROBLEM STATEMENT:
Better-enums currently does not provide a way to deliver its contents as
a Debian package

SOLUTION:
Added Debian packaging files

DETAILS:
Follows the standard Debian Packaging rules. See https://www.debian.org/doc/manuals/debmake-doc/index.en.html

IMPACT ANALYSIS:
When making future releases, debian/changelog needs to be updated

TESTING:

  • Ran dpkg-buildpackage -us -uc -b
  • Ran dpkc -c on resulting DEB file
  • Ran lintian on resulting DEB file
  • Installed resulting DEB file and compiled against it using pkg-config --cflags better-enums

PROBLEM STATEMENT:
Better-enums currently does not provide a way to deliver its contents as
a Debian package

SOLUTION:
Added Debian packaging files

DETAILS:
Follows the standard Debian Packaging rules. See https://www.debian.org/doc/manuals/debmake-doc/index.en.html

IMPACT ANALYSIS:
When making future releases, `debian/changelog` needs to be updated

TESTING:
- Ran `dpkg-buildpackage -us -uc -b`
- Ran `dpkc -c` on resulting DEB file
- Ran `lintian` on resulting DEB file
- Installed resulting DEB file and compiled against it using `pkg-config
--cflags better-enums`
@aantron
Copy link
Owner

aantron commented Sep 7, 2022

Thanks! I don't have the expertise to maintain this in-repo. I'm inclined not to merge it, but I suggest that you could publish this in a repo or package that you maintain, and we can add a link to that repo or installation instructions in this repo's README.

@gri6507
Copy link
Author

gri6507 commented Sep 7, 2022

Of course, this is completely up to you, since this is your project. However, the maintenance for this is minimal. When making a release, you simply have to update debian/changelog with minimal information about the release. It could be as short as just the release version/date, or you could opt to add release notes information there as well. The format of this file is very well documented (see https://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog for documentation and https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#changelog for annotated example).

I would be more than happy to help you maintain and test this file, if that makes things easier for you.

@BrainStone
Copy link

Shouldn't this be prefixed lib? As it's a library and that's the convention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants