> If you download a BINARY package, you are expected to READ and FOLLOW
> the instructions. If you don't do that, then don't expect to get
> anything but RTFM from me ;-)
Mike, I know how to build this, I'm trying to stop the onslaught of
emails from users, that's all.
> We have *one* Makefile.in file. The Makefile.maint file is not for
> "normal" users ('maint' = maintainer).
Which package has one Makefile.in? In 1.1.13_bin I see:
plucker-1.1.13$ find . -name Makefile.in
./Makefile.in
./docs/Makefile.in
./parser/Makefile.in
./parser/python/Makefile.in
./parser/python/PyPlucker/Makefile.in
./viewer/Makefile.in
./tools/pluck-comics/Makefile.in
./tools/Makefile.in
> Is it really that difficult to do "cd unix; ./install-plucker"? BTW,
> that works both for the binary package and the source package.
Alright, agreed. Now why is ./configure in there then? Ideally,
./configure should see that I'm on Linux/Unix, and then run
unix/install-plucker for me, like other similarly built packages do. Or..
simply spit out some text after testing that this is a binary-only package
that tells me what to do from here.
Anyway, back to screenshots and tutorials so I can get 1.1.13 up
today for everyone, assuming Nimda doesn't hit too hard. How bad is the
non-US Nimda onslaught?
/d
