Hello again everyone. I've run into a bit of a dilemma - The way I currently have things set up is three main projects, one called "common" and two others for two different products, which both inherit from common. Here's the issue. We have a lot of language-related packages - like Python 2.7 for example, and will be getting a lot of Node.JS related packages. I don't want "common" to end up being a complete mess and turning into what one of our current yum repos for one of the two products is - 3000 packages with no idea what's still in use, where they came from, etc... So, I'd ideally like to add in some more organization, but am afraid of messing up the repo setup for the two products. What would be the recommended way to handle this? Thanks. -Matt -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org