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

Re: Input on package thermometer (Was ... long ago: package thermometer improvements)



Hi,

On Sat, Jul 13, 2013 at 03:37:50PM +0200, Francesco P. Lovergine wrote:
> On Fri, Jul 12, 2013 at 05:50:55PM +0200, Paolo Cavallini wrote:
> > 
> > OK, I understand. So what is the best way to suggest the inclusion of a package?
> > The list at http://wiki.debian.org/DebianGis/PackageList looks oldish, and partly
> > duplicates the thermometer.
> > 
> 
> I see three possibilities: 
> 
> 1. using the current thermometer just to track possible
> additional package and linking the other tool for packages already available.

I personally would feel confused by two different thermometers.

> 2. updating the simple list on the wiki

Would be a simple solution.
 
> 3. adding an information about prospective package to the debian blend tool.

As I tried to explain:  For prospective packages you need to create the
following packaging files in VCS:

  debian/changelog (possibly featuring a "Closes: #<wnpp-bug-no>")
  debian/control  featuring
     Homepage
     Vcs-*
     Package(s)
     Description(s)

Nice to have:
  debian/copyrigth (DEP5 compatible skeleton featuring at least one License field)
  debian/upstream in case there are some scientific publications available)

In other words:  Creating two very simple skeletons of d/changelog +
d/control in your Vcs should be pretty simple to do.  Everything else
you need to do is just to inject the Package(s) into Debian GIS tasks
files.

> Of all them, I think the third one is the less viable, but maybe the more
> interesting. Andreas?

I'd prefer the third option because it is IMHO the most sustainable way
and if I did not yet managed to explain sufficiently enough what needs
to be done please ask in more detail what remains unclear. 

Kind regards

      Andreas.

-- 
http://fam-tille.de


Reply to: