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

Re: packaging LibreCAD (was: Bug#605914: Any news on this?)



Switching to debian-science as I seemed to made a mistake on the correct list 
for this :-)

On Sunday 17 April 2011 15:59:15 Scott Howard wrote:
[snip]
> > I am also CCing you, although I think you must be subcribed to this list,
> > please tell me if you are so as not to CC you.
> 
> I'm on the list, no need to cc: me

Great :-)

[snip]

> Check out [2,3] for how we use git.  

Excellent :-)

> the package should build with
> "git-buildpackage --pristine-tar" (after fixing the B-D you mentioned
> below.) We use pristine tar if you don't have the tarball, you just
> need to use that once and it will generate it. Once you have the
> pristine tar, you just need to use git-buildpackage on the cloned
> repo. I also use "git-buildpackage --git-tag" when releasing before
> uploading (this hasn't been uploaded yet, but a tag was created during
> git-importdsc when I imported in my first working copy, we we'll just
> have to ignore that tag for now)

OK :-)

[snip] 
> > - remove dxflib/ and fparser/ from the tarball, and add a correspodanta
> > README.source file.
> 
> Thanks, but I believe they are already removed. See the
> get-orig-source target of debian/rules, and see the master branch of
> the git repo, the upstream branch of the git repo, and the output of
> "pristine-tar checkout ../librecad_1.0~beta5+no-libs.orig.tar.gz" They
> all have been cleaned of third party libraries already.
> 
> we could change change the version from 1.0~beta5+no-libs to something
> like 1.0~beta5+dfsg. I was just using "no-libs" as a working name as I
> removed the libraries one by one.

Found it!
 
> We do need to mention it in the README.source file, so we could use yours.

Will apply it :-)

[snip]

> I wouldn't mind reviewing the patch, but you can also apply to the
> debian science team on alioth and get used to working with the git
> repos. 

I already done that some days ago (lisandropm-guest).
As for git, I think I will just have to learn git-buildpackage mostly.

> You can then even make your own branch that we can merge into
> the master branch, or you can commit directly to the main branch.
> Adding README.source, you to uploaders, and fixing B-D with dxflib
> should all be ok to commit directly onto the branch when you get
> access to the git repo.

Thanks Scott!

-- 
porque no respeta el orden natural en el que se leen las cosas
>¿por qué top-posting es tan molesto?
>>top-posting
>>>¿cuál es la peor molestia en los emails de respuesta?

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: