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

Fix naming inconsistency #39

Merged
merged 2 commits into from
Dec 13, 2022
Merged

Fix naming inconsistency #39

merged 2 commits into from
Dec 13, 2022

Conversation

CyrilBrulebois
Copy link
Contributor

While distribution packages are probably going to use an explicit name like crowdsec-custom-bouncer, it makes sense to have the Go import path match the location of the Git repository (as that's already done for cs-firewall-bouncer).

Note: This is definitely not a blocker packaging-wise (I already have a local patch anyway), I just have to make sure the Go-Import-Path declared in debian/control matches the declared module name to ensure the build is fine. I could do the opposite, and do cs-crowdsec- in the Go-Import-Path, whatever works for you is fine with me.

While distribution packages are probably going to use an explicit name
like crowdsec-custom-bouncer, it makes sense to have the Go import path
match the location of the Git repository (as that's already done for
cs-firewall-bouncer).
Copy link
Contributor

@sabban sabban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mmetc mmetc merged commit c9cbd0d into crowdsecurity:main Dec 13, 2022
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