Skip to content

Conversation

@FFY00
Copy link

@FFY00 FFY00 commented Apr 24, 2020

This allows distributions to properly build packages.

Signed-off-by: Filipe Laíns lains@archlinux.org

This allows distributions to properly build packages.

Signed-off-by: Filipe Laíns <lains@archlinux.org>
@FFY00 FFY00 force-pushed the makefile-install branch from c17400b to 9e8efd5 Compare April 24, 2020 14:26
@CyberShadow
Copy link
Owner

This is a breaking change, so I'm not sure about this. ZNC is most likely to be installed in /usr/bin.

I actually wrote the makefile for personal convenience. I'm not sure it should be in version control.

Perhaps use znc-buildmod directly and ignore the Makefile? This is what the AUR package does:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=znc-clientbuffer-git

Probably this isn't the first third-party ZNC module packaged for Arch. What do other packages do?

@FFY00
Copy link
Author

FFY00 commented Apr 24, 2020

ZNC will be installed in /usr/bin if it was installed via the package manager. Manual installs to /usr are not supported by any distribution that I am aware of.

If that is the case you should install the plugins via your package manager. You can always just change PREFIX when running make if you really want to.

Perhaps we could make this clear in the readme?

Yes, this is the first packaged ZNC module.

@FFY00
Copy link
Author

FFY00 commented Apr 24, 2020

Running znc-buildmod directly is fine, but having the makefile doesn't really hurt, it makes things easier.

@CyberShadow
Copy link
Owner

ZNC will be installed in /usr/bin if it was installed via the package manager.

Yes, I think this is the most likely scenario from the point of view of someone running this makefile - install the distribution-provided ZNC package, and then additional third-party modules from source using znc-buildmod.

If that is the case you should install the plugins via your package manager. You can always just change PREFIX when running make if you really want to.

Maybe we can detect the prefix where ZNC (or znc-buildmod) is installed? Or, alternatively, it would be great if we could make the makefile fail if the PREFIX is incorrect. Removing the -D flag to install would do that, except in the case of a DESTDIR, so that's a dead end.

My concern is that, with this change, running sudo make install in the situation above will look like it worked but actually do the wrong thing in a way that I think may be difficult to diagnose for a good portion of this project's target audience.

What do you think?

Yes, this is the first packaged ZNC module.

Considering the Makefile was a "non-stardard" addition and znc-bulidmod is the expected way to build a ZNC module, I think using the latter would set a more universal precedent.

@FFY00
Copy link
Author

FFY00 commented Apr 24, 2020

We can run znc-buildmod from the prefix, $(PREFIX)/bin/znc-buildmod. This also makes sure we are building with the correct binary and avoids version errors, etc.

@CyberShadow
Copy link
Owner

Yes, excellent idea!

@CyberShadow
Copy link
Owner

Does this look OK to you?

@FFY00
Copy link
Author

FFY00 commented Apr 24, 2020

Sorry, had to hop on a quick call.

Yes, it looks good.

@CyberShadow CyberShadow merged commit 2e32d50 into CyberShadow:master Apr 24, 2020
@CyberShadow
Copy link
Owner

Thanks! And also for packaging :)

@CyberShadow
Copy link
Owner

Tagged v1.0.48.

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.

2 participants