[Pkg-lirc-maint] svn hell night

Héctor García Álvarez hector at scouts-es.org
Tue Feb 6 11:08:20 CET 2007


El lun, 05-02-2007 a las 22:59 +0000, Stephen Gran escribió:
> Hi all,
> 
> So, mostly due to my own mistaken starting assumptions, I had done quite
> a bit of work based off the wrong tree, and made it very difficult to
> move forward.  So I spent a fair amount of time moving and reorganizing
> svn so that it makes sense (to me).
> 
> Right now, the structure is:
> /lirc/
>      branches/
>               etch/      # Branched from last upload - maintain for etch 
>                          # lifecycle
>               upstream/  # subdirectories for each new upstream version,
>                          # and current/
	- Since we have the tarballs directory this shouldn't be needed, should
we?

>      tags/               # Holds tagged release of debian/
>      trunk/              # Holds development tree of debian/
>      experimental/       # playground
>      build-area/         # technically, a build-area - do we need it?
	- Only for working with tarballs if we have only the debian/ dir on the
svn, but I normally have it locally. You can remove it if you wish and
mark it svn ignore
>      tarballs/           # upstream tarballs
	- You should get rid of upstream dir or of this one depends on the way
you decide to work, there is no much sense in having both.

> There are other directories under branches/, but I would like to get rid
> of them, as it's probably a mistake to assume a mapping between upstream
> version numbers and debian/ packaging scripts.
> 
> My plan going forward is to remove the extra directories under branches/,
> if no one has any objections, finish my changes to experimental/, and
> then merge them back to trunk/, delete experimental/, and finally do an
> upload to somewhere out of the way like experimental to get feedback.
> 
Good idea.

> Personally, I prefer having a trunk/ somewhere that has all the upstream
> source and all the debian/ source in it together - it makes it easy for
> me to work on a package, build it, clean it (check that clean actually
> results in no diff) and then commit changes, but I'd like to discuss
> that before doing it.  I'd also like to, after a discussion about this,
> commit a README or something to root of the tree explaining how each
> tree is meant to be used, so we don't get other newcomers like me
> getting so confused.
> 
I used to work like that and the changes on lirc to work with the
tarballs dir made by Aurelian or Julien showed me that it is much
cleaner to work in the tarball way and also easier to upgrade upstream
sources, although it took me some time.

If your choice it is because of tecnical issues (you don't know how to
do something), I can get with you on irc and show you how to use it all.
But if it just because you like it better the other way, go ahead, you
are the one working on it, all the rest of us will have to adapt.

> I am proposing a lot of upheaval, so if there are any objections, please
> speak up - I don't want to do things that will make people unhappy, I'm
> just trying to make it a system I understand.
> 
> Thanks all,
Thank you for doing the work.
I you have msn and want to reach me to talk, I use my debian email as my
msn account id.

Regards,

Héctor




More information about the Pkg-lirc-maint mailing list