Re: execline-2.3.0.3 failes with ./configure --prefix=
On Mon, Oct 23, 2017 at 04:39:38AM +, Laurent Bercot wrote: > > > ./configure --prefix=/package/admin/$(basename `pwd`) > > If you're using slashpackage, don't use --prefix. > Use --enable-slashpackage instead. If I understand it well, I am supposed to make the symlinks myself from /package/prog/skalibs-2.6.0.2 to /package/prog/skalibs right? Jean exec ./tools/install.sh -D -m 644 src/include/skalibs/unixonacid.h /package/prog/skalibs-2.6.0.2/include/skalibs/unixonacid.h exec ./tools/install.sh -D -m 644 src/include/skalibs/webipc.h /package/prog/skalibs-2.6.0.2/include/skalibs/webipc.h root [ /sources/skarnet.org/skalibs-2.6.0.2 ]# cd ^C root [ /sources/skarnet.org/skalibs-2.6.0.2 ]# cd .. root [ /sources/skarnet.org ]# cd execline-2.3.0.3 root [ /sources/skarnet.org/execline-2.3.0.3 ]# ./configure --enable-slashpackage checking for C compiler... ... gcc checking whether C compiler works... ... yes checking target system type... ... x86_64-unknown-linux-gnu ./configure: error: /package/prog/skalibs/sysdeps is not a valid sysdeps directory root [ /sources/skarnet.org/execline-2.3.0.3 ]#
Re: execline-2.3.0.3 failes with ./configure --prefix=
./configure --prefix=/package/admin/$(basename `pwd`) If you're using slashpackage, don't use --prefix. Use --enable-slashpackage instead. -- Laurent
Re: execlineb's import conflicts with ImageMagick
Guillermo: This is known, see the 'execline-2.3.0.0' section of this announcement: * https://www.skarnet.org/cgi-bin/archive.cgi?2:msp:1687:blbgbjnpebcmhkmelgjd And these: * https://lists.debian.org/debian-user/2017/10/threads.html#00164 * https://lists.debian.org/debian-devel/2017/10/threads.html#00127
Re: execlineb's import conflicts with ImageMagick
On Sun, Oct 22, 2017 at 09:32:30PM +, Charles Duffy wrote:
> Given as GraphicsMagick moves "import" to a subcommand ("gm import"), you
> might consider using it to avoid any conflict.
Thank you for the input. I do not use
GraphicsMagick (yet), and I have just tried
installing skarnet tools into /usr/bin then I
found the conflict as I used --prefix, now I am
back to install it directly, later I will switch
to slashpackage.
I am using this Lisp script to simply install all
tools by:
install-s6.lisp skalibs-2.6.0.2.tar.gz etc.
as all s6 tools are consistent, it simply works.
(unless *args* (quit))
(setf files *args*)
(defun remove-tar.gz (file)
(substring file 0 (search ".tar.gz" file)))
(dolist (file files)
(let* ((command1 (format nil "tar xf ~A" file))
(command3 (format nil "cd ~A && ./configure && make && make install"
(remove-tar.gz file
(shell command1)
(shell command3)))
> > The ImageMagick software has the "import" command
> > that is conflicting with "import" from execlineb
> > package.
> >
> > Jean
Re: execlineb's import conflicts with ImageMagick
Alright, thank you, that is solved. On Sun, Oct 22, 2017 at 07:06:13PM -0300, Guillermo wrote: > Hello, > > 2017-10-22 18:01 GMT-03:00 Jean Louis: > > > > The ImageMagick software has the "import" command > > that is conflicting with "import" from execlineb > > package. > > This is known, see the 'execline-2.3.0.0' section of this announcement: > > * https://www.skarnet.org/cgi-bin/archive.cgi?2:msp:1687:blbgbjnpebcmhkmelgjd > > G.
Re: execlineb's import conflicts with ImageMagick
Hello, 2017-10-22 18:01 GMT-03:00 Jean Louis: > > The ImageMagick software has the "import" command > that is conflicting with "import" from execlineb > package. This is known, see the 'execline-2.3.0.0' section of this announcement: * https://www.skarnet.org/cgi-bin/archive.cgi?2:msp:1687:blbgbjnpebcmhkmelgjd G.
Ansible integration for nosh service management
Hello, Integration for nosh service management has been added to the "system" modules of Ansible's development branch[1]. The nosh module can set running and enabled state for user or system-wide services[2], in a similar fashion to other service management modules. Testing feedback and suggestions are welcome. Archlinux users may find the nosh toolset packaged in the Archnosh repository[3]. Debian, FreeBSD and OpenBSD users should look to the packages provided by the author of nosh[4]. Regards, [1] https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/system/nosh.py [2] https://docs.ansible.com/ansible/devel/nosh_module.html [3] https://framagit.org/taca/archnosh [4] https://jdebp.eu/Softwares/nosh/debian-binary-packages.html https://jdebp.eu/Softwares/nosh/freebsd-binary-packages.html https://jdebp.eu/Softwares/nosh/openbsd-binary-packages.html
