Hi Brian, On Thu, Dec 8, 2011 at 12:00 AM, Brian Gernhardt <[email protected]> wrote: > On Dec 6, 4:53 pm, Lex Trotman <[email protected]> wrote: >> On Wed, Dec 7, 2011 at 3:10 AM, Brian Gernhardt <[email protected]> wrote: >> > 1) No matter what your DESTDIR or prefix, it attempts to install in / >> > etc/vim. I was installing into my personal directory and this caused >> > errors. >> >> The vim stuff has to go in wherever vim wants it, but configure should >> have an option to disable that since some of us are virulently >> anti-vim (oh, and you need sudo/root to write to /etc). > > Installing outside of DESTDIR is extremely unfriendly to packagers, at > the very least.
That is always going to be the case if installing a package instals extensions to another tool as well, it has to write to the other tools location. > > But "where vim wants it" is only useful to the sysadmin. Us poor > users trying to install things need things in places like $HOME/.vim > and dislike it when the install fails just because it can't install > to /etc when I never asked it to. Ditto. Probably the best solution would be for Stuart to take install-vim out of the default target but maybe also extend the test to also test the directory is writable rather than failing. > >> > 3) The install-sh provided by asciidoc itself can't install more than >> > one file at at time, but is constantly used that way. I fixed this by >> > wrapping every use of INSTALL_PROG and INSTALL_DATA in a for loop. >> >> I don't see where it is used with multiple files, sounds like your >> make is non-standard and is trying to use one command to do all >> targets rather than running the command for each target. > > It's hidden behind some environment variables: > > $(PROGTARGETS): % : $dir > $(INSTALL_PROG) $($@) $(DESTDIR)/$($<)/ > > expands to (in one instance) > > prog : progdir > ./install-sh -m 755 asciidoc a2x.py $(DESTDIR)/$(bindir)/ Huh, I always thought $@ ran a separate recipe for each target, well there you go. However configure requires (and is supposed to check) that install conforms to the multiple files to single directory behavior. Pity it doesn't check the install-sh conforms, but it assumes you use the one that comes with it, which does accept many inputs. I suggest Stuart upgrade his install-sh to one from a recent autotools package :) Cheers Lex > > Similarly when using $(INSTALL_DATA) to install the files from $ > (docbook), $(dblatex), etc. > > ~~ Brian > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/asciidoc?hl=en. > -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
