Hi, On 08/21/2015 02:49 PM, Marcus Rückert wrote: > we have 4 options of packages using gems > > 1. the good way: just requiring system gems and having nothing intree > > 2. the bad way: Buildrequires for the gems and then copying them into > their tree. > > 3. the ugly: having all gems locally in the package as sources > > 4. the bad and ugly: a mix of 2 and 3
As discussed, going forward it is probably the best to talk about the packaging policies to achieve #1. This could be supported with the appropriate rpmlint checks if someone would like to pick this up. > another option might be to look at all the binary rpms and see if you > find any gems outside of the system gem dir (gem env gemdir). also keep > an eye out for packages which have multiple gem files in their binary > rpms. those are probably bundling too. but bundling into the gemdir. The last option will help me solve the task at hand and should be easy enough to implement. The dependency generator will not be required as submitted. Thanks, Andreas -- Andreas Stieger <[email protected]> Project Manager Security SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
