From: "Ludovic Courtès" <ludo@gnu.org>
To: "yarl baudig" <yarl-baudig@mailoo.org>
Cc: Julien Lepiller <julien@lepiller.eu>, 59845@debbugs.gnu.org
Subject: [bug#59845] [PATCH 0/4] Add PMB (Integrated Library System)
Date: Sun, 25 Dec 2022 18:26:25 +0100 [thread overview]
Message-ID: <87pmc7wg1q.fsf@gnu.org> (raw)
In-Reply-To: <ea-mime-63a56432-4d4d-141e6f09@www.mailo.com> (yarl baudig's message of "Fri, 23 Dec 2022 09:17:54 +0100 (CET)")
Hi,
"yarl baudig" <yarl-baudig@mailoo.org> skribis:
>> >
>> > Now, I see one solution to avoid the copy (and the chown), apart from the
>> very first activation. That's keeping even more state into http-directory :
>> for example a file ".version" with the hash of the pmb package used inside.
>> That way we know if there's really an upgrade. What do you think?
>>
>> It sounds like it’s going a bit far in terms of complexity.
>>
>> Why do we need to copy these files every time? Do they actually have to
>> be writable? If not, whatever this copying step is doing could be done
>> in a ‘computed-file’.
>>
>> Does that make sense?
>>
>
> Hmm no, not really. Yes it has to be writable for the interactive initialization through web browser to take place. At least two operations take place there that need RW :
> 1/ renaming of both install.php and install_req.php.
> 2/ saving into a file the url and credentials for connexion to the database.
Credentials have to be handled out-of-band anyway (keep in mind that
/gnu/store is world-readable so in general we cannot have password in
transit via the store).
> There is no _need_ to copy every time. I did like this in my first patchs because it was _correct_ (I didn't think about efficiency then).
>
> That's why I am proposing the solution which copy only for the very fist activation and for the first activation after a package upgrade (or downgrade).
>
> I don't see how we could avoid this. I don't think it's a good idea to try to avoid the interactive installation as it gives informations and options on the installation to the user.
OK.
> Why "computed-file"?
Take it with a grain of salt because I still have an incomplete
understanding of the initialization process of PMB.
My thought was that, if there’s a “computation” (copying files around,
renaming some) that can be done once and for all, then we could do that
in ‘computed-file’. But what you’re saying, IIUC, is that this is not
done “once and for all”.
HTH,
Ludo’.
prev parent reply other threads:[~2022-12-25 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 21:48 [bug#59845] [PATCH 0/4] Add PMB (Integrated Library System) Yarl Baudig
2022-12-05 21:52 ` [bug#59845] [PATCH 1/4] gnu: php: Add '--enable-soap' configure option Yarl Baudig
2022-12-05 21:52 ` [bug#59845] [PATCH 2/4] gnu: Add PMB Yarl Baudig
2022-12-05 21:52 ` [bug#59845] [PATCH 3/4] gnu: Add PMB service Yarl Baudig
2022-12-05 21:52 ` [bug#59845] [PATCH 4/4] doc: Add Integrated Library System section Yarl Baudig
2022-12-09 11:52 ` [bug#59845] V2 yarl baudig
2022-12-09 11:53 ` [bug#59845] [PATCH v2 1/4] gnu: php: Add '--enable-soap' configure option Yarl Baudig
2022-12-09 11:53 ` [bug#59845] [PATCH v2 2/4] gnu: Add PMB Yarl Baudig
2022-12-20 14:56 ` [bug#59845] [PATCH 0/4] Add PMB (Integrated Library System) Ludovic Courtès
2022-12-09 11:53 ` [bug#59845] [PATCH v2 3/4] gnu: Add PMB service Yarl Baudig
2022-12-20 15:03 ` [bug#59845] [PATCH 0/4] Add PMB (Integrated Library System) Ludovic Courtès
2022-12-09 11:53 ` [bug#59845] [PATCH v2 4/4] doc: Add Integrated Library System section Yarl Baudig
2022-12-20 15:13 ` [bug#59845] [PATCH 0/4] Add PMB (Integrated Library System) Ludovic Courtès
2022-12-22 17:18 ` yarl baudig
2022-12-22 22:40 ` Ludovic Courtès
2022-12-23 8:17 ` yarl baudig
2022-12-25 17:26 ` Ludovic Courtès [this message]
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=87pmc7wg1q.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59845@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=yarl-baudig@mailoo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.