Skip to content

Allow build with systems libenet#159

Closed
susnux wants to merge 1 commit intoassaultcube:masterfrom
susnux:system_enet
Closed

Allow build with systems libenet#159
susnux wants to merge 1 commit intoassaultcube:masterfrom
susnux:system_enet

Conversation

@susnux
Copy link

@susnux susnux commented Jun 26, 2016

Make it possible to build with system libenet, so packaging is easier.
This is already done by Arch Linux or openSUSE.

@ac-stef
Copy link
Member

ac-stef commented Jun 26, 2016

Unless those distributions plan to synchronize future updates of their enet packages with the release dates of AC, this is a horrible idea.
The enet library in use is part of the AC game protocol - which is the reason for us to have enet sources included in our package in the first place.
If Arch or oS actually mess up AC by using a different enet library, I'm going to give their maintainers' home phone numbers to everyone who comes to us with a support case because of this!.
Don't build packages, if you don't know what you're doing!

@susnux
Copy link
Author

susnux commented Jun 26, 2016

Of cause, but normally if the protocol changes also the version of enet changes so the .so number will change.
You can have multiple different versions of libraries on your system so there should be no problem if there are different versions.
(The packagers should of cause keep track on changes and require the matching version).

@ac-stef
Copy link
Member

ac-stef commented Jun 26, 2016

Why on earth should we open that can of worms just to eliminate 50k of static library? (Also, 1.2.0.2 already fails on some platforms, because it requires an old version of libcurl.)

Just think of it as a code part of AC that looks very much like a commonly known network libarary.

Btw: recent development versions are no longer compatible to stock enet anyway :)

@susnux
Copy link
Author

susnux commented Jun 26, 2016

Ok.
I tested this patch with the current git head (feb 27) and with enet7 (1.3.13).
No problems after some hours of playing the game :-)

@ac-stef
Copy link
Member

ac-stef commented Jun 26, 2016

a) "it's working now" is irrelevant, as long as you can't guarantee the system enet library to stay compatible
b) last year, our enet code received a security fix that will not be fixed in the official enet sources
c) our enet sources already provide API extensions that are in use by commits that have not yet been merged with the main repository (check my branch "pit")

There is absolutely nothing to gain for us by using the system lib for enet.
Instead, we would open up a potential support hell.

@ac-stef ac-stef closed this Jun 26, 2016
@susnux
Copy link
Author

susnux commented Jun 26, 2016

Ok

@susnux susnux deleted the system_enet branch June 26, 2016 21:44
This was referenced May 26, 2018
@aurhat aurhat added the Arch package bug https://github.com/assaultcube/AC/pull/159 label May 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Arch package bug https://github.com/assaultcube/AC/pull/159

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants