(keeping Stefano in Cc in case he's not subscribed) On Tue, Apr 19, 2011 at 09:14:30AM +0200, Patrick Schoenfeld wrote: > On Mon, Apr 18, 2011 at 11:25:12PM +0200, Benjamin Drung wrote: > > I like to get involved in the maintenance of devscripts. There are some > > things that I like to do: Reduce the delta to the Ubuntu package, > > refreshing the packaging (simplifying debian/rules for example), adding > > test cases that are run on package build time, and last but not least > > getting scripts from ubuntu-dev-tools into devscripts. > > Sounds good, mostly. However, there is still a decision to be made if > we'd like to have python scripts in devscripts. I know that James > expressed concerns about the maintenance of python scripts by the > current team.
Aside from what I mentioned on the -devel thread, I'm also hesitant due
to wanting to reduce code duplication.
For Wheezy, I'd like to work on consolidating common code among the
scripts into relevant Perl modules. The first piece being the code that
handles parsing the config files, command-line options and environment
variables to determine a script's runtime parameters. This code is
complex and replicated in essentially every perl script, so having a
more declarative interface with the complexity hidden from the main
scripts should be helpful.
Having a common language makes this easier and I've been considering
looking over some of the shell scripts to see which ones would most
benefit from being re-written in Perl to take advantage of the future
config module as well as modules from libdpkg-perl.
> Personally I would not mind python scripts in devscripts.
> As all in the team know my time is very limited, so my opinion shouldn't be
> crucial, but I wouldn't mind to support them aswell.
I'm not strictly opposed to Python, but I'd like to weigh its use
against goals such as the above. If we do start including Python
scripts, then IMO we would need feature parity between the devscripts
libraries in both languages.
I should be getting some more time[0] to devote to Debian starting in
May, so I can provide more guidance around this as well as working more
on the bug backlog.
> > Is there any documentation or guidelines that I should know? Should I
> > push my changes into the master branch and they will get reviewed there
> > or should I use a separate branch?
>
> Usually maintenance of devscripts follows common sense and is centered
> around communication in the IRC channel. If you plan to make bigger
> changes which may have a greater impact its probably a good idea to
> create a local branch and merge it into master after intensive testing
> and after coordination with the team.
Agreed. If you'd like to stage changes in a personal repository on
git.d.o and get reviews first as you get familiar with devscripts and
Perl, I'd be glad to work with that. That's something I can assure I'll
give time to on a routine basis.
> > PS: Does a list archive exists of this mailing list?
>
> There used to be one on teams.debian.net AFAIR, but its down since a
> while. However mailarchive.com is keeping an archive [1]..
Interesting, mailarchive seems to do a better job than gmane[1]. For
some reason gmane doesn't seem to get responses to bugs.
[0]: I'm finishing my current semester of school at the end of April,
but I'm also getting closer to my wedding, the preparation of which
may partially offset time gained from not being in school.
[1]: http://news.gmane.org/gmane.linux.debian.devel.devscripts
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[email protected]>
signature.asc
Description: Digital signature
