[pkg-wpa-devel] changing pkg-wpa SVN layout

[Kel Modderman]

On Monday 02 April 2007 17:18, Reinhard Tartler wrote:
> >
> > 1) svn-injecting the packages into the archive
>
> Frankly, I'm surprised that svn-buildpackage still does not support our
> current directory layout.

It may do, but its not obvious to me how I would tell svn-bp about the 
non-standard layout. Moreover, since hostapd was added to our archive, the 
layout didn't really suit anyway.

> I use svn-buildpackage in the debian games 
> team, but always preferred to do upgrades without svn-inject, because
> IME, that script wasn't as reliable as I expected. Perhaps things have
> changed, but honestly, I'm perhaps not a strong svn fan and therefore
> didn't look closer at it.

I use it a lot, its worked pretty good for me in the past.

>
> > 2) moving existing tagged releases into respective tags area
> > 3) removing old, obsoleted archive contents
> > 4) updating to level README
> >
> > Any objections?
>
> Since in the past, it was mainly you who upgraded new upstream version,
> I think choosing a svn layout which is comfortable to you is a good
> idea. The switch sounds pretty painfull to me, however :/

Should not be too painful. (i hope)

>
> > I'd like to do this soon (as in next couple of days), I'm growing tired
> > of manually updating upstream and manually tagging releases when tools
> > exist to automate this kind of maintenance => svn-buildpackage. And if
> > these tools are not your thing, the new layout changes nothing; you are
> > not forced to use the tools.
>
> Right.
>
> Btw, as an informal poll, have you already used git? I haven't yet, but
> I noticed that hostap upstream has recently switched to git and I wonder
> if it was a good idea to use it for our packaging work as well. I expect
> that this would make cherrypicking changes from upstream easier.

No, I am also a git virgin. Indeed, it would be kinda handy to use now that 
Jouni uses it has his VCS of choice.

The main turn-off i've gathered from various blogs and mailing list comments 
about it have been a mixed bag, and most criticise its documentation. But 
hey, I certainly did not learn SVN by reading the redbook, I just learnt by 
using it, I guess the same will apply to git.

There is a git service offered to debian developers now no? If so, we should 
definitely consider using it (git ;-) in the future, or at least have a go at 
setting up our packaging stuff and see how we like it. What do you think?

Have you come by any resources describing debian package maintenance and git 
that are worth a look? I just grabbed git-buildpackage, it looks like an 
extremely familiar tool.

Thanks, Kel.