From: Guillermo <gdiazhartusch@gmail.com>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: nosh version 1.37
Date: Mon, 19 Feb 2018 00:12:46 -0300 [thread overview]
Message-ID: <CADQ2Nw8FLvvFULQxsFU_8C-ed4q9eM_tTQHQaJAx3fAG+NuMvg@mail.gmail.com> (raw)
In-Reply-To: <298aba59-cfda-5a51-0541-67720dd794b5@NTLWorld.COM>
2018-02-18 20:05 GMT-03:00 Jonathan de Boyne Pollard:
>
> Guillermo:
>
>> This is going to happen for every [GNU/]Linux distribution that is not
>> Debian, Arch, CentOS or RHEL. It does not... uh... look very portable :/
>>
>
> That is a reflection of reality. It isn't very portable. But you are
> misidentifying what it is.
> [...]
> Guillermo:
>
>> Additionally, the convert/per-user/*.do scripts' 'read_os' function calls
>> 'exec' via absolute path /bin/exec instead of relative path ../../exec,
>> which is not going to work if nosh isn't already installed (chicken and
>> egg).
>>
>
> There's no chicken and egg problem. The external formats configuration
> import requires (amongst others) the nosh-exec package.
> [...]
> Moreover that is not the relative path from your
> $HOME/.config/service-bundles/convert/ directory to /bin. Not that there
> of course *is* a stable single relative path for such a thing, given that
> home directories can be anywhere from /export/home/guillermo to
> /var/lib/mysql . Nor that, as mentioned, such a relative path is needed,
> given that one installs the toolset before running the external
> configuration import.
But wait. You are talking here about run-time requirements / behaviour
of the configuration import subsystem and the service bundles provided
by nosh, after one installs (some equivalent of) the nosh-bundles or
nosh-run-via-systemd packages for the target operating system. I
accept that OS-specific patches might be required here and there to
make them work for the reasons you mentioned.
But the 7 .do scripts I talked about are executed (indirectly) by the
package/compile script from the source package, and they just create
symbolic links. To be precise, they are executed by the source/all.do
script, because they are named in 'echo' commands that feed their
output to the 'xargs -r redo-ifchange' invocation. As it is, on any
[GNU/]Linux distribution that is not Debian, Arch, CentOS or RHEL,
downloading the source package and building it slashpackage-style by
executing package/compile will simply fail.
There are warnings in the jdebp.eu webpage about package/stage, but my
expectation was that package/compile would just work (even without a
previous nosh installation), as it has for older versions, provided
the required dependencies are installed (meaning redo, xmlto, ncurses,
pax, etc.). I can work around this by just patching source/all.do so
that it does not execute those .do scripts, or look at what they
should do for Gentoo and patch them, or whatever, but I am sure quite
a few people besides me are going to be surprised by package/compile
failing for them.
(You are right about relative path ../../exec being wrong, it should
be relative to redo's working directory, i.e. ./exec)
G.
next prev parent reply other threads:[~2018-02-19 3:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54430B41.3010301@NTLWorld.com>
[not found] ` <54B86FD5.3090203@NTLWorld.com>
[not found] ` <554E53EF.4080600@NTLWorld.com>
2015-05-09 23:09 ` nosh version 1.14 Jonathan de Boyne Pollard
2015-06-01 0:02 ` nosh version 1.16 Jonathan de Boyne Pollard
2015-06-28 15:19 ` redo version 1.2 Jonathan de Boyne Pollard
2018-02-18 6:39 ` redo version 1.4 Jonathan de Boyne Pollard via freebsd-hackers
2015-06-28 16:39 ` nosh version 1.17 Jonathan de Boyne Pollard
2015-06-28 16:55 ` pflog(8) manual page bug Jonathan de Boyne Pollard
2015-06-28 20:55 ` Warren Block
2015-08-20 13:01 ` nosh version 1.18 Jonathan de Boyne Pollard
2015-08-22 18:04 ` nosh version 1.19 Jonathan de Boyne Pollard
[not found] ` <CADQ2Nw-506S3Gm4s40t+WzJu3Wzpwp=wPBWCFoQGZ2yrctCM_w@mail.gmail.com>
2015-09-28 1:05 ` nosh version 1.20 Jonathan de Boyne Pollard
2015-09-28 1:33 ` Joe Maloney
2015-09-28 7:27 ` Jonathan de Boyne Pollard
2015-10-05 5:39 ` nosh version 1.21 Jonathan de Boyne Pollard
2015-11-02 2:15 ` nosh version 1.22 Jonathan de Boyne Pollard
2015-12-17 13:50 ` nosh version 1.23 Jonathan de Boyne Pollard
2016-01-13 9:25 ` nosh version 1.24 Jonathan de Boyne Pollard
2016-02-01 1:03 ` nosh version 1.25 Jonathan de Boyne Pollard
2016-05-06 23:19 ` nosh version 1.27 Jonathan de Boyne Pollard
2016-08-06 17:30 ` nosh version 1.28 Jonathan de Boyne Pollard
[not found] ` <a1646fa5-e64c-5b2d-b057-aa347d1f30a1@freebsd.org>
2016-08-21 11:04 ` Jonathan de Boyne Pollard
2016-08-30 15:58 ` Joe Nosay
[not found] ` <0c339dcb-d09b-f234-d37f-9521d97146b1@NTLWorld.com>
[not found] ` <d9dddf06-257f-2f5e-c7dd-99cfd6aba187@NTLWorld.com>
[not found] ` <CADQ2Nw8YbeHp-yOUxTBXn6H8_OrU74ab1nb5=gc-+xeBL4FWFw@mail.gmail.com>
[not found] ` <159edb67-0288-a07e-c2cb-76574d0d2b98@NTLWorld.com>
[not found] ` <CADQ2Nw-XksEtP_wrXtaRFKw0yM=A-0okfXxFOpyDiCQGptQEww@mail.gmail.com>
[not found] ` <5769980e-cdc3-b802-b704-fdb8d0ce3f8f@NTLWorld.com>
[not found] ` <CADQ2Nw95KwkwDDErc_wsLrg=rHjhKHRsfseFPhA9avS0siu+5Q@mail.gmail.com>
2016-12-03 11:33 ` nosh version 1.29 Jonathan de Boyne Pollard
2016-12-03 11:41 ` Jonathan de Boyne Pollard
2016-12-31 23:53 ` nosh version 1.30 Jonathan de Boyne Pollard
2017-01-14 11:26 ` nosh version 1.31 Jonathan de Boyne Pollard
2017-01-30 9:09 ` nosh version 1.32 Jonathan de Boyne Pollard
2017-04-09 19:52 ` nosh version 1.33 Jonathan de Boyne Pollard
2017-07-05 20:41 ` nosh version 1.34 Jonathan de Boyne Pollard
2017-09-10 10:43 ` nosh version 1.35 Jonathan de Boyne Pollard
2017-12-11 8:03 ` nosh version 1.36 Jonathan de Boyne Pollard
2018-02-18 6:49 ` nosh version 1.37 Jonathan de Boyne Pollard via freebsd-hackers
2018-02-18 21:23 ` Guillermo
2018-02-18 23:05 ` Jonathan de Boyne Pollard
2018-02-19 3:12 ` Guillermo [this message]
2018-02-19 5:10 ` Jonathan de Boyne Pollard
2018-02-20 19:13 ` Jonathan de Boyne Pollard
2018-02-21 1:21 ` Guillermo
2018-02-21 7:53 ` Jonathan de Boyne Pollard
2019-01-23 4:51 ` nosh version 1.39 Jonathan de Boyne Pollard
2019-03-20 10:21 ` nosh version 1.40 Jonathan de Boyne Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADQ2Nw8FLvvFULQxsFU_8C-ed4q9eM_tTQHQaJAx3fAG+NuMvg@mail.gmail.com \
--to=gdiazhartusch@gmail.com \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).