On Sun, Apr 08, 2001 at 09:22:27PM +0200, Robert Bihlmeyer wrote: > > Do you guys see any value in me trying to keep up a "most wanted" page > > for tasks that everyone can work on? I can't remember (or find the > > email of the person) who got apt to work, but it was great to say > > "Here's what's needed" and have someone actually take the task. > > I provided the patch in bug 92025, if you mean that. The thing is, > most snags are really small things: if a package has compiled once, > failure in newer versions are usually quite easy to fix. Normally the > whole affair doesn't take more than 30 minutes.
It's still valid and valuable work to do this, thanks!! > > However, this will be a commitment of time to keep it going, and I'd > > rather not do it if it won't get used. > > Personally, I don't find it necessary. I'm perfectly fine with the > Turtle pages. Here's my how-to for people looking for small > maintainance hacking (open to enhancements): > > 1. Look at > <URL:http://people.debian.org/~jbailey/turtle/group/Debian/index.html> or > <URL:http://people.debian.org/~jbailey/turtle1/group/Debian/index.html> > Packages with a red status need work. There's also non-us in there, under turtle1. > Things would help making the Turtle pages even more useful: > > * failing build dependencies should be mentioned up front. For > example, a lot of packages failed due to no working cdebconf [fixed > now], but I only discovered that after looking through a lot of > build logs. The build dependancy stuff isn't well integrated into the turtle yet, so I don't think Marcus could write these any more obvious yet. Maybe in his next version (I think he's in exams now). > * add more packages. Perhaps I'm insane, but having everything of > "standard" or higher priority under Turtle would be quite a > blessing. Resource constraints may prevent that, though. They do a little. Part of the problem is that packages that fail to build never advance to "purge" stage. I have about 300 megs worth of cruft sitting on `turtle' right now, because there's uncompiled (or worse, half-compiled) source code sitting there. The other problem is that the load is split over 2 turtles right now, and I'll be adding more as I can. I need to work on that dispatcher so that we can have everything on one web page.
