From: "Laurențiu Leahu-Vlăducu" <l.leahu-vladucu@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/1] Better explain the situations where it makes sense to adapt the rustup configuration
Date: Mon, 16 Dec 2024 12:32:59 +0100 [thread overview]
Message-ID: <b97c3250-d276-4bcf-b683-64c63d3414e1@proxmox.com> (raw)
In-Reply-To: <D6D2YVIIRYRM.2U38MGC7ONXC0@proxmox.com>
On 16.12.24 12:15, Shannon Sterz wrote:
> On Mon Dec 16, 2024 at 12:01 PM CET, Laurențiu Leahu-Vlăducu wrote:
>> This patches adds some explanations about the situations where it makes sense to adapt the rustup configuration.
>> While this is not necessary if the Debian rustc package is used, it makes sense in case a newer / beta / nightly
>> compiler should be used for testing. The current documentation was worded in such a way that it sounded
>> as if rustup should always be set, which is not necessary unless additional compilers have to be used.
>>
>> This patch replaces "[PATCH proxmox-backup] Remove mentioning rustup in README.rst because it's no longer needed"
>> as discussed here: https://lists.proxmox.com/pipermail/pbs-devel/2024-December/012105.html
>>
>> Signed-off-by: Laurențiu Leahu-Vlăducu <l.leahu-vladucu@proxmox.com>
>> ---
>> README.rst | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/README.rst b/README.rst
>> index 0caa9874..81957533 100644
>> --- a/README.rst
>> +++ b/README.rst
>> @@ -5,8 +5,10 @@ Build & Release Notes
>> ``rustup`` Toolchain
>> ====================
>>
>> -We normally want to build with the ``rustc`` Debian package. To do that
>> -you can set the following ``rustup`` configuration:
>> +We normally want to build with the ``rustc`` Debian package (see below). If you still want to
>> +use ``rustup`` for other reasons (e.g. to easily switch between the official
>> +stable, beta, and nightly compilers), you should set the following ``rustup`` configuration
>> +to use the Debian-provided ``rustc`` compiler by default:
>>
>> # rustup toolchain link system /usr
>> # rustup default system
>
> hm this is now wrapped at 100 chars (as is standard for our rust source
> code), but for .rst files we seem to use wrapping at 80 chars afaict.
> the rest of the file is also wrapped at 80 chars (with some small
> exceptions). so i think i'd prefer it if your patch stuck to the 80
> chars here.
>
You are right, thanks for the info. I have now sent a second version of
my patch where the lines are wrapped at 80 chars.
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2024-12-16 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 11:01 Laurențiu Leahu-Vlăducu
2024-12-16 11:15 ` Shannon Sterz
2024-12-16 11:32 ` Laurențiu Leahu-Vlăducu [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=b97c3250-d276-4bcf-b683-64c63d3414e1@proxmox.com \
--to=l.leahu-vladucu@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/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 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.