[php-apt-parser-maint] Proposal of directory structure

[Daniel Leidert]

Am Samstag, den 13.05.2006, 20:31 +0300 schrieb Jarno Elonen:

> > ChangeLog and/or NEWS
> > README
> > LICENSE
> > parse-apt-files.inc
> > examples/* (CGI script, PHP and CSS files using the script)
> 
> Looks good, but I'd prefer LICENSE instead of COPYING if it's not GPL.

Ok. Removed in the above proposal.

> Maybe 
> it would also be a good idea to also provide a fully working example in the 
> examples directory (index.php, CSS, some small example .debs + a shell script 
> for building the Packages and Sources files[1])?

Yes. No problem. We could also reference a few examples, where the
script is used.

> I'm still not sure about the .deb. Do you have some idea about Debian 
> integration for it?

I e.g. reference it for debarchiver in one of the READMEs [2]. I guess,
users of mini-dinstall, debpool, reprepro and probably users auf
automatic repositories (dpkg-dev and apt-utils) could use it [3][4]. So
these packages are probably the ones, which could suggest such a deb.

> I still feel that this sort of small script doesn't 
> really deserve a full Debian package - especially since its user base could 
> be perhaps a hundred people or so - at most.

Of course, such a package would not be of the biggest main public
interest. But suggesting it by the right packages could increase the
amount of users. ATM I think about the following idea:

- putting the script itself into /usr/share/php to allow to include it
in php files
- creating a config-file based CGI-script, which generates a package
overview of the given paths (the "further development" of Damians
CGI-script)

This is a nice tiny package. Users always get the latest script version
and I can remove any text-based references and instead reference a
complete package with documentation. I think, there is an interest in
your script :)

[2] /usr/share/doc/debarchiver/README.repository.gz
[3] http://foss.stat.unipd.it/mediawiki/index.php/Debian_Mirror_Setup
[4] Just search for parse-apt-files.inc at Google to get an overview.
Even our German "Debian Anwenderhandbuch" references your script and
Ubuntu users use it too.

So my suggestion: We put your script into trunk, move the changelog from
the head into ChangeLog and create an AUTHORS and THANKS file in good
old GNU manner - or if we decide to package it: ChangeLog gets
debian/changelog and LICENSE/AUTHORS/THANKS gets debian/copyright. Then
we make a copy and create a branch, where we put the latest version with
Damian's patches. And in this branch, we can test for a Debian package
and check the changes, Damian and I did.

Regards, Daniel