[Privoxy-devel] OK to move the winsetup dir under current?

[Ian Silvester]

I see your point about one-stop shop, and it's true I've seen many other
projects with per-platform subdirs within the source tarball. I'm okay
with this change so long as we do it for all platforms we still support
- I'm not keen on different approaches per platform. Fabian, David, what
do you think?

I also take your point about cvs; seems we're stymied unless/until we
replace Sourceforge with a repository at privoxy.org - Fabian is that
still the plan?

Ian


On Tue, 15 Aug 2017, at 21:17, Lee wrote:
> On 8/15/17, Ian Silvester <iansilvester at fastmail.fm> wrote:
> > I see the advantages, but this change would 'pollute' the core code
> > tarball with platform-specific code, which'd be a shame I think.
> 
> One could look at it as one-stop-shopping instead of pollution :)
> 
> What other open-source projects require more than downloading just the
> tarball/zipfile to build?  There's probably a lot, but all I can think
> of is VLC right now..
> 
> > ... Is
> > there no scope to refactor the code in winsetup to reduce the gymnastics
> > required at build time?
> 
> Once you get the proper directory structure there's no gymnastics.
> Getting the proper structure is a bit of a pain, but no big deal.  ...
> except I'm getting weird about using clear-text protocols and
> cvs -z3 -d:pserver:anonymous at ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa
> co winsetup
> has the traffic unencrypted with no way of verifying what was
> downloaded.  If someone wants to register on SF they can do
> export CVS_RSH=ssh
> cvs -z3 -d:ext:SFuserid at ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co
> winsetup
> but requiring them to register on SF first seems to be asking a bit much.
> 
> Is there some other way a random user can get the code over an
> encrypted channel?
> 
> Lee
> 
> 
> > Ian
> >
> > My PGP public
> > key[http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc]
> >
> > On Tue, 15 Aug 2017, at 15:13, Lee wrote:
> >> I'm updating the 'how to build on windows' documentation & it would
> >> make things much easier on the windows side if the winsetup/ directory
> >> was under current/ instead of being at the same level.
> >>
> >> 1. It would be included in the source tarball at release time
> >> 2. It would get tagged with the version number at release time
> >> 3. No extra gymnastics required for doing a release build on windows
> >>
> >> Anyone have a problem if I move it under current?
> >>
> >> Thanks
> >> Lee