The GNU guys said i should apply that installation method.
They wont accept my install.sh.

EG:
Tui shall be installable by: (as i understood them)

Code:

./configure --prefix=XY
make && make install

---------- Post updated at 18:39 ---------- Previous update was at 17:54 ----------

Well they mentioned i could write my own ./configure, as long it supports make install.
Failing to get make working with the regular tools, makes it even harder to write my own ./configure, as i do not understand the process/requirement yet.

Me not asking for a solution, a direct link to where it explains the actual 'install' (cp, mv, chmod, etc) process requirements would be very apreciated.
Best i have is the doc_DATA = Readme.md part, which doesnt seem to be right, as the make fails (see above).

---------- Post updated at 19:55 ---------- Previous update was at 18:39 ----------

Let me do a practical example, what i tried to achieved using this guide:
autoconf automake tutorial
Which already fails at point 2, as there are no Makefile.in, removed/renamed as suggested by guide, but required by autoscan.

typescript:

Code:

Script started on Mon Jun 29 21:41:45 2015

0 ~/prjs/tui $ ls
bin   lists  templates  tmp        build-rpm-tui.sh  install.sh  tui.spec        typescript
docs  man    themes     README.md  gen-autoconf.sh   stats.sh    tui_compl.bash

0 ~/prjs/tui $ ./gen-autoconf.sh ## Sumarizes that guides steps 1-4
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE [^\}]*}/ at /usr/bin/autoscan line 361.
autoscan: cannot open < Makefile.in: No such file or directory
mv: cannot stat 'configure.scan': No such file or directory

1 ~/prjs/tui $ ls
bin   lists  templates  tmp        autoscan.log      gen-autoconf.sh  stats.sh  tui_compl.bash
docs  man    themes     README.md  build-rpm-tui.sh  install.sh       tui.spec  typescript

0 ~/prjs/tui $ exit
exit

And the log is empty.

Code:

$ cat autoscan.log 

0 ~/prjs/tui $

Weird thing is, i did get (somehow) a generated Makefile.in, sadly i dont remember how.
Most confusing part for me is: Guide tells to 'remove' the Makefile.*'sm while autoscan seems to require one.

Which 'one' is true?
Specialy, since the offical docs, dont mention the requirement for Makefile.in (n)either...
(2.4.1) :: https://www.gnu.org/software/automak...tml#Hello-Worl

Been on this for a week now, and not further a single bit, as what i started to feel/think i had understood is in question again.

Any advice please?

---------- Post updated at 21:41 ---------- Previous update was at 19:55 ----------

oh wait, i understand it now...
Are you saying that i should not use autoscan/autoconf to create, but 'continue after' the creation of configure.ac?

This said, it helped to get rid of the 'focused' mind....

I now have this to get started on new projects:

Code:

#!/bin/bash
clear
tui-yesno "Are you in the project directory ($(pwd))?" || exit 1
## Write basic configure.ac
cat > configure.ac <<-EOF
	AC_PREREQ([2.69])
	AC_INIT([TUI], [0.9.0], [erat.simon@gmail.com])
	AM_INIT_AUTOMAKE([-Wall -Werror foreign])
	AC_CONFIG_FILES([
	 Makefile
	 docs/Makefile
	])
	AC_OUTPUT
EOF

## Write makefile in project root
cat > Makefile.am <<-EOF
	AUTOMAKE_OPTIONS = foreign
	SUBDIRS = docs

	compldir = \$(datadir)/bash-completion/completions
	compl_DATA = @PACKAGE_TARNAME@_compl.bash
EOF

## Write makefile in docs
tui-bol-dir docs ; cd docs
cat > Makefile.am <<-EOF
	doc_DATA = LICENSE
EOF
cd ..

## Finalize?
tui-yesno "Run automake now?" || exit
aclocal
automake --add-missing
autoconf

## Final test?
tui-yesno "Test now?" || exit
./configure --prefix=/usr && \
	make && \
	tui-asroot "make install"

Which seems to be working fine, and providing a very basic minimal example to copy/install files.

yay
/solved

Now asking myself why it took me so long to get (t)here...
Have a good evening and thanks for reading.