search

dinhvh / libetpan

Mail Framework for C Language
www.etpan.org
Other
612 stars 283 forks source link

provide a proper release tarball #141

Open qmx opened 10 years ago

qmx commented 10 years ago

Currently the tarballs under releases are just plain repository exports. This means that you need to have autotools installed on the target machine for consuming the build.

one of the ways of fixing this is by just running make dist during the release process and uploading the generated tarball to github's "draft a new release". 20140527-atl6z-20140527-cyky3-new release

This way I can contribute a homebrew recipe for installing libetpan properly.

Thanks a lot for libetpan!

mones commented 6 years ago

Unfortunately another release made and still ignoring this issue :-(

pmetzger commented 6 years ago

autotools are in homebrew. Just depend on them and run them. I do something similar in MacPorts, it works fine. There's nothing much wrong with just having a repo export, IMHO.

mschwendt commented 6 years ago

Anything wrong with the 1.9.1 source release?

1.9.1 fails to build on Fedora. After compiling everything it ends with a missing libetpan.so, because it's a dangling symlink in the ./src/.libs directory where libetpan.so and libetpan.so.20 point at a missing libetpan.so.20.2.0 file. Haven't had a chance to look into it further yet.

/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -O2 -g -W -Wall -ULIBETPAN_DLL -lz -o smime smime.o ../src/libetpan.la -lz -llockfile -pthread libtool: link: gcc -g -O2 -O2 -g -W -Wall -ULIBETPAN_DLL -o .libs/smime smime.o -pthread ../src/.libs/libetpan.so -ldb-5.3 -lsasl2 -lz -llockfile -pthread -Wl,-rpath -Wl,/usr/local/lib gcc: error: ../src/.libs/libetpan.so: No such file or directory

pmetzger commented 6 years ago

It works fine for me on MacPorts. I didn't have to change anything in the build recipe from 1.8.

pmetzger commented 6 years ago

BTW, I will repeat: I think the way the current releases are built is totally fine. Needing autotools is hardly a serious inconvenience. Most serious devs end up needing to install them anyway, and as a system packager, depending on them for build is trivial.

dinhvh commented 6 years ago

It sounds like I'm not doing a great job at it. Would love if someone could jump on helping with it. Please reach me out if anyone is interested in fixing it!