Em Quarta-feira 16 Junho 2010, às 17:24:06, Dave Neary escreveu: > 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 > packaging)
There are three kinds of patches in the current .src.rpm:
1) patches from kde-qt (older qt-copy) that are either backports of upcoming
releases or patches submitted and are pending acceptance
2) patches from kde-qt that have been rejected by the Qt team
3) patches that I had never seen before, which I have to assume also split
into "backports", "rejected" and "unsubmitted"
The kde-qt patches have a bugtracking number so we can easily find out why they
are (still) there. The #3 patches are not as forthcoming.
What worries me is the fact that MeeGo is carrying rejected patches and
unsubmitted ones.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
