Re: [fontforge-users] Announcing LibSpiro - version libspiro_beta.0.3.20150131

On Feb 10, 2015, at 2:37 AM, Matijs van Zuijlen wrote:

> On 09/02/15 21:00, Jose Da Silva wrote:
>> I take it that most problems are resolved now, except for adding C99 and  
>> providing a ./configure or rewording INSTALL?
>> 
>> Did the configure provided work okay? I'm uncertain what to expect from a 
>> newer OS building a configure to run for an older OS on another platform.
>> 
>> Will providing a ./configure branch be okay? vs adding in trunk/HEAD?
> 
> Isn't it just much simpler to check in ./configure in master as opposed to
> maintaining a separate branch? Autoconf is supposed to create cross-platform
> configure scripts.

It's generally considered an antipattern to check configure and other generated files into version control. Instead, create an automated way (e.g. a Makefile target) to create them. Create also an automated way (e.g. another Makefile target) to package up a compressed tarball containing the entire source including these generated files. Whenever you tag a new version of your code in your repository, upload a corresponding compressed tarball to a server where users can download it (e.g. github's release infrastructure).


------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html