[MeeGo-dev] Qt 4.7 packaging for MeeGo 1.1
dneary at maemo.org
Wed Jun 16 08:24:06 PDT 2010
Thiago Macieira wrote:
> So my question is: how should this process be?
The easiest thing to do is to include a spec file, and a "make rpm" target.
In any case, the "unknown patches" shouldn't be unknown, you *should*
get a .orig and a .patch (which should be little more than compile
options and a spec file). If there are any more consequential patches
than that, your choice is
(a) contact the patcher to see why he's making changes, and if there's a
good reason then integrate them
(b) ignore the patches, and continue to ship just the tarball
(c) decide to take over the rpm package building and run the risk of
alienating a volunteer packager (if, indeed, it's a volunteer doing the
> More likely than not, in option 2, there would be no patches applied to Qt and
> it would be a stock & pristine build. (Note: the current patches are unknown
> to us, so this option also implies that they go away unreviewed)
I think reviewing any patches in the MeeGo rpm build is a mandatory step
there - as I said, typically there are no patches, other than adding a
spec file that is LSB conformant for where files should be put and so on.
Email: dneary at maemo.org
Jabber: bolsh at jabber.org
More information about the MeeGo-dev