Quoting Bill Nottingham (2013-01-28 20:51:04)
Stanislav Ochotnicky (sochotnicky(a)redhat.com) said:
> > I would assume that, even with approval, there's no way to stage these
> > changes before the mass rebuild?
> There's too many packages I guess. It's likely we won't be able to
> *all* packages. If we manage to convert core let's say 300-400 I'll be happy
> consider this all a success since that will mean we'll test the code in most
> possible situations.
> Some simple packages could be converted automatically, but verification might
> actually ake longer than just doing it manually :-)
OK. Do we have an examples of 'common things you might need to know to
migrate your packages', 'how to verify your migrated package', etc? (Then
if it's just going to be a few people in the Java SIG doing most of the migrations,
it may not be necessary.)
I am not sure if Mikolaj (author of XMvn) aimed for it originally, but I'd love
it if this solution became more widespread in Linux/Java world. We'll have a
talk about it during FOSDEM this Saturday.
We have some semi-automatically generated documentation:
It's not finished yet, and could definitely use some polishing and fixes.
Besides the cookbook I'd like to document common pitfalls and things to check.
Mainly regarding automatic requires generation, file ownership and compatibility
> At this point I'm happy with automatic requires (which will
likely keep us
> occupied to make sure unnecessary stuff doesn't creep in everywhere)
Nah, that never happens! :)
Indeed, Freemind in Fedora doesn't pull in whole Eclipse :-)
Stanislav Ochotnicky <sochotnicky(a)redhat.com>
Software Engineer - Base Operating Systems Brno
Red Hat Inc. http://cz.redhat.com