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

Bug#749815: Package updated



> Il Martedì 9 Settembre 2014 15:12, Gianfranco Costamagna
> <costamagnagianfranco@yahoo.it> ha scritto:

> >As you might have noticed the new poedit releases uses lucene++
> >library, this is why in the last few weeks I focused in packaging it.
> >
> >I finally (with great help from Tobi) achieved this goal, and the
> >library is waiting in ftp NEW queue [1]
> >

-------------- 8< --------------
> >
> >The new releases are "huge" in size terms, so I removed the "deps"
> >directory from the source tarball prior to the import (don't know
> >why upstream bundles lucene/wx/boost/... making the source something
> >like 700MB (uncompressed).
> >
> >The debian/copyright still needs to be updated, but I'm pushing the
> >changes to let you know the progresses I did and collaborate on the
> >same repository.
> 
> the copyright is up-to-date now.
> 
> I also switched to autoreconf,
> 
> waiting for a review :)
> 

I have two initial comments (Without having done an in-depth review):

We could create an alioth project including a mailinglist, and use
that mailinglist as maintainer, and put us all as uploaders. It might
ease collaboration, if we just need one email to remember for
maintenance questions. What do you think? (Also, I'd like to use my
@debian.org email for package maintenance).

You have removed a whole lot that has no use in the package such as
embedded libraries (Which is good) - but you could have made an
"Files-Excluded"-entry in the copyright for this. This would make those
files be removed when using something like "git-importorig --uscan"
also, automating the entire importing process and removing the need to
remove files "by hand". This also adds the benefit that you just need
to add the files that are to be removed once, and simply update the
list for each upstream release, if more unwanted files are added to the
upstream tarball that we need to remove.

See https://wiki.debian.org/UscanEnhancements
for information on this. The wikipage mentions "Problematic copyright",
but this is of course useful in our case too.

-- Andreas Rönnquist
gusnan@gusnan.se


Reply to: