Hi, On Mon, Sep 14, 2009 at 09:19:00PM +0200, Sven Joachim wrote: > On 2009-08-28 22:18 +0200, Sven Joachim wrote: > > On 2009-08-27 14:57 +0200, Sebastian Harl wrote: > >> On Thu, Aug 27, 2009 at 01:11:09PM +0200, Sven Joachim wrote: > >>> I don't know who will pick up ncurses, but if it is going to be a team I > >>> would like to help. > >> > >> I really think something like ncurses should be team maintained. I'd > >> also be glad to join any such team, however, I probably won't find any > >> time to work on that before the end of September. > > > > Until we find co-workers, I have set up a preliminary git repository at > > Alioth as an appetizer: > > > > http://git.debian.org/?p=users/joachim-guest/ncurses.git;a=summary > > > > Not much there yet, I'm still finding out how the package works. Would > > probably have been a little easier if Daniel had not thrown his work > > away. :-( > > During the past two weeks, I have been studying the package, triaged > some of the bugs and made several changes. See the Debian changelog and > the commit logs for what I've broke. Cool! Looks like you've put quite some work into that. Thanks! > There are some other things that could/should be done, but for which I > would like other people's opinion/help: > > - Switch to quilt from dpatch? While I strongly prefer quilt, I've seen > that you use dpatch for your packages, so I held back changing the > patch system. I don't have a strong opinion on that. We use quilt for rrdtool as well, so go ahead with that if that's your preference. > - Give the Debian patches meaningful headers. Finding out where the > patches came from and whether they are still necessary probably > requires digging deep into ncurses' history. That sounds like a very good idea but I expect that to be quite some work. I don't think this has to be finished before doing the next upload but should rather be improved as time permits. Unfortunately, the changelog does not mention any of the patches by name but it mentions that some patch has been introduced for some purpose. Using that information, it should be possible to get the patch descriptions right. > - Move ncurses5-config to libncurses5-dev (and ncurses5w-config to > libncurses5w-dev) to fix #480437? I hesitate to remove files from an > essential package, although that change is unlikely to break anything. Hrm … I fully agree that *-config belong into the respective -dev packages but I also agree that removing some binary from an essential package might be dangerous. Maybe we should put that on debian-devel? > - Write a manpage for ncurses-config and submit it upstream, or generate > one automatically with help2man. Sounds good. Should not be that hard. > - Split off HTML documentation and examples into a separate package, say > ncurses-doc, to save space in the archive (see #233400). Agreed. > - Update our terminfo files debian/*.ti. For xterm.ti I have already > done that, but I'm not familiar with the other terminals. I'll look into that and see what else I can do. > - Reintroduce some of the /usr/share/doc symlinks where policy allows > this. The Ubuntu approach of deleting the upstream changelog from > some binary packages is not to my liking. I'm not in favor of removing upstream changelogs either. We could use a symlink for that, though, since it's rather big. > Should I try to register an Alioth project for ncurses? The name > pkg-ncurses seems to be good for it, and we could use git as SCM and > move my personal repository to the project. That was my idea as well. I hope, I'll find some time to work on the package next week, once my diploma thesis is done. Again, thanks for all the work so far! Cheers, Sebastian -- Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/ Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
Attachment:
signature.asc
Description: Digital signature