It's been included as part of sys-cluster/torque since the 4.1 series and no one seems to have complained on those archs that Torque has the extra keywords for. Thanks,
(In reply to Justin Bronder from comment #0) > It's been included as part of sys-cluster/torque since the 4.1 series You mean a future version of torque will depend on the split off library package? > and no one seems to have complained on those archs that Torque has the extra > keywords for. Extra keywords for what?
* Detected file collision(s): * * /usr/include/uthash.h * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-cluster/torque-4.1.5.1-r1:0::gentoo * /usr/include/uthash.h
(In reply to Jeroen Roovers from comment #1) > (In reply to Justin Bronder from comment #0) > > It's been included as part of sys-cluster/torque since the 4.1 series > > You mean a future version of torque will depend on the split off library > package? That's the plan, I'm sitting on patches to allow it to use the system version of uthash instead of the included one. > > > and no one seems to have complained on those archs that Torque has the extra > > keywords for. > > Extra keywords for what? torque has keywords for alpha, hppa and ia64. Uthash does not. I'm hoping that as torque worked on those archs, uthash should be ok to keyword.
Why don't you fix the bugs first and then present a combination of separately built torque/uthash for people to test? There is little point in keywording uthash when the only thing in the tree that might use it actually conflicts with it and should block installing it. So where is the torque ebuild that uses this? Where is the block on <torque-versions that provide uthash?
(In reply to Jeroen Roovers from comment #4) > Why don't you fix the bugs first and then present a combination of > separately built torque/uthash for people to test? There is little point in > keywording uthash when the only thing in the tree that might use it actually > conflicts with it and should block installing it. > > So where is the torque ebuild that uses this? Where is the block on > <torque-versions that provide uthash? Sure, I can do it this way if you prefer. I just figured that once uthash was keyworded I could then push the new version of torque with the correct dependencies. Right now I'm unsure of how to do that aside from adding a blocker and waiting until uthash has the full set of keywords. So, to make sure I understand what you want: 1. Add blocker for uthash to torque 2. Wait for keywords 3. Update Torque to depend on uthash and not use the internal copy.
The common procedure goes like this: 1) Put the new split-off library in the tree and make it block older versions of the ebuilds that use it "internally". 2) Put a new ebuild in the tree that depends on that library, and drop keywords on that ebuild that can't resolve the new dependency. 3) Ask for keywords to be restored for both the library and the new ebuild. This way people can test the new torque ebuild against the split-off library ebuild. And you don't need to wait at all to put the new torque ebuild in the tree.
Ok.
