[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: libnet - orphaning libnet

On Fri, 27 Mar 2009 21:33:25 +0200, Stefanos Harhalakis wrote:

> On Friday 27 March 2009, David Paleino wrote:
> > F/up set, please respect it
> > (I forgot setting it in my first mail, sorry.)
> Being a user of kmail I don't really know if it is possible to easily handle 
> it. Also, I'm not suer I completely understand what you mean. You want to 
> only send replies to the debian-devel list? (If yes, excuse this reply :-)

Yes, that was the intention :)
Ok, stripping unwanted CCs now.

> > > I see that you use git. Is it madantory to use git? (I'm not familiar
> > > with it).
> >
> > No. You (or whoever is going to maintain it) may use whichever $VCS you
> > want. There's some old-ish SVN repository for libnet (I migrated it to git
> > recently, so the history there is not that old -- if you meant to use SVN,
> > that is)
> >
> > http://svn.debian.org/viewsvn/collab-maint/deb-maint/libnet
> >
> > But please note that the SVN repo is quite "broken" [0] -- you may want to
> > remove it and start it all over again (maybe re-importing it from git?)
> I have to have this stored in an VCS? For some other packages i packaged
> (only 1 in debian), i used a local copy (at least to begin with).

Not really, it's just "best practice" -- in case of an harddisk failure you'll
still have all your work in a VCS. But you can always only have local copies (I
started using VCS's soon after starting packaging, I believe I had only a few
only locally)

> If yes: Do I have to have the whole package in the VCS or just the debian/ 
> directory? From what I've read I assumed that I only need to have local 
> copies (or a versioning system) of debian/.

That depends on the chosen VCS / workflow.

In case of SVN, seems like being best practice to only store debian/ (and
you'll see that libnet's repo doesn't respect this -- and I can't recall why).

In case of Git, many developers use a three-branch-layout ("upstream",
containing the unpacked sources, "pristine-tar" containing a compressed version
of the sources, and "master", containing debian/ merged with the "upstream"
branch -- you usually work only on "master", and branch from there, i.e.
upstream and pristine-tar are usually handled by automagical tools). Other
developers use a debian/ only (i.e. "master" only) layout, which I'm personally
not comfortable with.

After all, it's your choice, you should have fun working with VCS's (that's why
I switched from SVN to Git most of my packages, *grin*)


 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

Attachment: signature.asc
Description: PGP signature

Reply to: