On Wed, Aug 19, 2009 at 02:02:07PM -0400, Luis Useche wrote: > Do I have to do something else here? It seems like this discussion > cooled down a bit. Is the patch in review? Is the patch been > considered for inclusion? Are there any changes I can do to make more > suitable for inclusion? I don't exactly how these things work and if I > followed the regular path to submit the patch. > > Thanks, > > Luis
You should direct your efforts in other directions. There are lots of things that are considered *not finished* in the current pkg tools, I'm slowly working on them, I have my list of stuff to do, and I won't look at your patches for now, because I have enough to tweak first, and getting this kind of functionality in right now is probably not a good idea. Ask again in six months, hopefully a lot of things will have settled down. I haven't ever had time to write the full picture of what's going on. Basically, I re-designed the pkg tools to accomplish certain goals, and offer certain guarantees. Perl means that I can do agile refactoring. My initial goal was to allow for updates, which no BSD supported at the time, to be as reliable as possible, and to be quite fast without building any extra information. The current design is surprisingly succesful at that. While working with updates, we discovered a few limitations, because some update patterns are just too weird to be true (dependency inversion, for instance), and because there's some stuff we did not predict (files moving from kdelibs to kdebase). So my current focus is to get these corner cases to work without having to cheat (which is what we currently do) and to get updates to feel faster (by merging the update discovery part with the actual update). This would also help people running -current, since one annoying "feature" of current is that you can't install new packages without updating your whole system first (the new update scheme would allow you to install a new package and check for updates on its dependencies only). The devil lies in the details: this is more complicated than it sound, so I'm refactoring more stuff to get rid of special cases so that it stays relatively bug-free (if you think about all the cases pkg_add currently handles, you'll notice that it's not THAT simple). So, yeah, I'm interested in feedback, but I can't be responsive on every part of it...