[geos-devel] Re: [postgis-devel] Re: CVS to SVN move

[Charlie Savage]

How would you do that in automake?

Here is where it is coming from:

SUBDIRS = \
	tests

EXTRA_DIST = \
	python.i \
	geos.pth

#MAINTAINERCLEANFILES = geos_wrap.cxx
#MOSTLYCLEANFILES = geos.py
CLEANFILES = geos_wrap.cxx geos.py

if ENABLE_PYTHON

BUILT_SOURCES = geos_wrap.cxx

python_DATA = geos.pth
pkgpython_PYTHON = geos.py
pkgpyexec_LTLIBRARIES = _geos.la


Charlie

Mateusz Loskot wrote:
> Paul Ramsey wrote:
>> The usual issues apply to putting generated files into the repository:
>> if different people with different swigs generate these files they will
>> potentially clobber each other in the repository and even generate
>> conflicts.
>>
>> A checks out
>> B checks out
>> A generates and updates and commits
>> B generates and updates, conflict!
> 
> Yes, this is the same situation as keeping ./configure script in the
> repo and then every run of autogen.sh will introduce problems.
> 
> If geos.py is generated file, then 'make dist' could operate this
> file optionally, depending on SWIG wrappers are build or not.
> 
> Best regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.osgeo.org/pipermail/geos-devel/attachments/20060726/de937717/smime.bin