On Apr 22, 2012, at 7:39 PM, "Dmitry V. Levin" <l...@altlinux.org> wrote:

> On Sun, Apr 22, 2012 at 06:21:18PM -0400, Jeffrey Johnson wrote:
> [...]
>> There's 124 patches in Mandriva Cooker headed towards
>> @rpm5.org in need of review. This check-in was the first
>> tentative step forward.
> 
> Wouldn't it be a good idea to review these changes prior to committing
> them?  This approach requires additional work, but it may be worth doing.
> I noticed that people are more disposed to let raw commits go in projects
> with post-commit review practice.
> 

Yes: no way am I just gonna swallow all those patches as is
at a dead run.

>> Your C expertise is welcomed in code reviews.
> 
> I must admit that commits of "ugly quick & dirty integration" quality
> do not encourage potential code reviewers.
> 

Yes: the patches are being integrated from @rpm.org for
"compatibility". Instead of rewriting (and hard-wiring
paths and patterns in C), the whole framework should
be swiped. You cannot be more "compatible" than by
stealing the original implementation.

Please note the fault is rather more complex than Per Oyvind's
coding or "ugly" comments. There is no "feature" set and
few criteria about what is needed.

>> As much as your input on a ROADMAP is welcomed.
> 
> Could you give me a reference to the current ROADMAP, please?
> 

The candidate ROADMAP items are at
        http://launchpad.net/rpm
see the blueprints. The priorities are more or less accurate
as of January. Ask if you wish more detail on any
item.

(aside)
Meanwhile this month's priorities (for me) were
        specspo replacement (using embedded sqlite3)
        automating typelib(…) dependency generation
        removing RPM_I18NSTRING_TYPE (RPM_STRING_TYPE instead)
        adding set:versions
Next month I'm likely going to have to attempt a replacement
for Berkeley DB licensing using either sqlite3 or ODBC. The
harder problem will be designing the SQL schema, not the implementation.

But these are merely tasks, not ROADMAP, which was *supposed*
to have been finalized in January (but crafting a ROADMAP
for RPM isn't simple: everyone wants something different.)

73 de Jeff
        
> 
> -- 
> ldv

______________________________________________________________________
RPM Package Manager                                    http://rpm5.org
Developer Communication List                        rpm-devel@rpm5.org

Reply via email to