[Privoxy-devel] How to identify when new files are added to the release?

[Ian Silvester]

On Wed, 26 Oct 2016, at 10:09, Fabian Keil wrote:
> Ian Silvester <iansilvester at fastmail.fm> wrote:
> 
> > Is there a standard way in which one can identify whether new files have
> > been added to the Privoxy release? The OS X packaging tools all require
> > each payload item to be uniquely referenced, and consequently the client-
> > tags file has been missing from my releases since it was added to the
> > project. I am consequently concerned that there are other files still
> > missing and that current OS X releases might still have missing
> > functionality as a result.
> 
> I assume most packagers use the install target with an empty
> DESTDIR and check what's installed.
> 
> In theory missing template files are also detected by
> privoxy-regression-test but in case of the client-tags
> template I forgot to add the test in time for the release.
> 
> Finally, you could look at the packaging lists used on other platforms,
> the one used for FreeBSD-based systems is available at:
> https://svnweb.freebsd.org/ports/head/www/privoxy/pkg-plist?view=markup
> 
> Note that it does not include the FAQ and the developer manual
> and packages for other platforms may not contain other files that
> aren't essential for Privoxy to work.

Thanks, that is all useful.

> > Separately, Fabian does http://www.privoxy.org/sf-download-mirror/ get
> > updated automatically as the Sourceforge file hierarchy changes? I've of
> > course replaced the OS X packages there with corrected versions and want
> > to ensure all download locations are updated.
> 
> At the moment it's updated manually by me (and I've done that),
> but hopefully every packager will be able to upload his own packages
> before the next release.

Ideal.

> BTW, for future package updates it would be preferable if the
> old packages would be kept instead of being overwritten. A revision
> number in the file name would make it more obvious for users of the
> old package that they should update.

I considered that - in future I will do so.

Cheers,

Ian