[SERVER-43036] Why are there different tgz binaries for multiple linux distros? Created: 26/Aug/19 Updated: 01/Oct/19 Resolved: 01/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Phillip Wirth | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi there,
I am one of the maintainers of https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo which downloads the mongod binaries extract it and fires mongod up to test some code against it.
It does download the legacy linux tgz file for that - https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-4.2.0.tgz for example.
However since 4.2.0 there is no legacy linux tgz anymore... Well it was legacy
Why are there different tgz binaries for multiple linux distros? - shouldn't the code be identical? What would be a useful replacement, since I can't install a real package or anything that requires root privileges.
Thanks in advance |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 27/Aug/19 ] |
|
Hello pwirth, Our blog post on ending the generic linux package implies why there are differences between the different OS builds:
A primary difference between OS-specific packages is how we link the system packages to MongoDB. Are you unable to use any OS-specific package in your use-case? |