2011/2/24 Tobias Gerschner <tobias.gersch...@gmail.com>: > Good Morning, > > I've just asked Jeff and Ralf for write access to the cvs repository of rpm. > I just like to briefly introduce me and what my motivation is on > participating with rpm development. > Being the lead dev of the yoper linux distribution for a couple of years I > had my fair share of dealings with rpm and while its a great piece of > software it's been abused beyond reach ( in Jeffs words : have it your way ) > and has from my point of view conceptually not evolved for some years > (IMHO) because of too many directions its been pulled to. > To see the progress of rpm5 over its short lifetime has been great and it > has always been bugging me that I am not contributing. After a recent > vacation I came with new strength and tackled an idea that's been floating > between Matthew Dawkins and me for a few years by now. Details can be found > here, with an excellent writing from Derrick Devine > . http://unity-linux.org/unity-and-yoper-a-tale-of-two-distros/ . For the > technically minded please read through to the end to the links section .... > That is where I'll see my main focus over this year and as with openpkg > we're a stakeholder in how RPM evolves and would not only like to demand but > also give something back. > Personally I want to focus on getting a feature into rpm which I believe > would have a great impact on the (ab)usability of rpm. I believe it is > feasible to use the FHS standard to create a templating system that allows - > in a very flexible way - the extension of the spec file markup %package and > related %files. Seeing that there is a filetrigger implementation ( great > improvement btw!) it should be possible to fire that off optionally during > e.g. __os_install_post to expand the list of packages and dynamically > populate a new subset of packages purely based on file presence in > %{buildroot}. > I've tossed the idea around for a year by now, but never gotten around to > working on it. I am not much of a C programmer to be honest, but I could > pick that up over time. In the meantime I'll focus on the ruby elements of > rpm and will happily fix anything that's reported broken - be it code or > concept. > However, I am pretty fluent in ruby and since it's a great language for > modelling and prototyping I believe it is a good match to get new ideas into > an rpm branch quickly before considering implementation in head. > I know that Eric has been working on ruby bindings over the last year and > maybe there's another chance for collaboration / reflection etc. > I'll be happily abused along the way if you have any comments or input.
Welcome aboard, I look forward to see you clean up my fugly ruby code soon. ;) -- Regards, Per Øyvind ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
