[SERVER-19434] Add version entry to both Community and Enterprise RPM packages to allow for dependencies regardless of type Created: 16/Jul/15  Updated: 26/Apr/16  Resolved: 26/Apr/16

Status: Closed
Project: Core Server
Component/s: Build, Packaging
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Eoin Brazil Assignee: Ernie Hershey
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Sprint: Build 12 (04/01/16), Build 13 (04/22/16), Build 14 (05/13/16)
Participants:

 Description   

Is it possible to add an additional field to our RPM packages that could indicate just "mongodb-server" without Enterprise or Community as a means of highlighting a dependency for MongoDB itself? This could be with or without a corresponding version number.

EDIT: This may be possible using a virtual package specified with a provides tag per this RPM feature.

The current output of the Community RPM returns:

$ rpm -q mongodb-org-server --provides
config(mongodb-org-server) = 2.6.10-1
mongo-10gen-server
mongodb-org-server = 2.6.10-1

The proposal would be:

$ rpm -q mongodb-org-server --provides
config(mongodb-org-server) = 2.6.10-1
mongo-10gen-server
mongodb-org-server = 2.6.10-1
mongodb-server

The current output of the Enterprise RPM returns:

$ rpm -q mongodb-enterprise-server-2.6.10 --provides
mongo-10gen-enterprise-server
mongodb-enterprise-server = 2.6.10-1.el7

Similarly for the Enterprise RPMs, the proposal would be:

$ rpm -q mongodb-enterprise-server-2.6.10 --provides
mongo-10gen-enterprise-server
mongodb-enterprise-server = 2.6.10-1.el7
mongodb-server



 Comments   
Comment by Ernie Hershey [ 26/Apr/16 ]

Sounds good. Thanks Eoin!

Comment by Eoin Brazil [ 26/Apr/16 ]

Hi ernie.hershey sorry I missed this update until now, you can close this out with your change as suggested on Jul 16. Thanks!

Comment by Ernie Hershey [ 16/Jul/15 ]

I believe this can be done with the current package definition by depending on the file /usr/bin/mongod, which is implicitly provided by both mongod packages because they include that file.

Is there a downside to that approach or a use case that it wouldn't cover?

Generated at Thu Feb 08 03:50:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.