under
> ~/.cache/guix/checkouts.
Thank you for the detailed explanation.
> Maybe a specific environment variable would do?
Perhaps. What is the threat model of the attacker?
--
Suhail
it/config under guix "authentication") and the
code updated to read the preference from there.
--
Suhail
bian, correct? Or is that not the
case? In other words, on Debian, does the systemd unit reference
=/var/guix/profiles/per-user/root/current-guix/bin/guix-daemon= ?
--
Suhail
Suhail Singh writes:
> FWIW, as an openSUSE Tumbleweed user, I believe Tumbleweed users who
> don't care if there is an easy way to uninstall Guix would be better
> served by using =guix-install.sh= as opposed to =zypper=.
Btw, for completeness, on Tumbleweed, the user needs to
h, in my opinion, is the
lesser evil.
On a related note, it would help if Guix would install manpages in
addition to infopages. Not sure if this omission constitutes a bug or a
missing feature.
--
Suhail
tsi.
>
> Will the Jitsi link be shared somewhere (here, irc, ...) for those of us who
> are
> not able to sign up on the page?
Could the Jitsi link also be shared on the mailing list and/or noted on
the libreplanet wiki?
--
Suhail
applied, either by the QA mechanism or a reviewer.
Assuming there aren't any objections to these tags, what are the next
steps? If my understanding of Debbugs Usertags is correct it seems we
can simply start using them? Though noting the above in the manual
would be helpful. However, that still leaves open the issue of how the
automated setting of tags is accomplished.
Thoughts?
--
Suhail
meone speaking on behalf of FSF)
in it.
--
Suhail
Please let me know in case the issue
persists, or you notice others (though, perhaps, off list).
--
Suhail
ing the above tools at present?
Or are there some reasons (over and above their lack of familiarity with
the above tools) that would prevent them from doing so?
--
Suhail
k to the bug with a
> diff - showing what was done.
I see. Thank you for sharing. I believe being more didactic with "new
users" would be good for the community.
--
Suhail
ml_node/Debbugs-Usertags.html>
> It would be great to agree those - try them for a bit - and document
> them in a 'howto' so that everyone uses the same process.
In addition to documenting the tags in the "Debbugs Usertags" section of
the manual, it would help for there to be a "howto" which focuses more
on the transition between the tags (i.e., the contribution workflow).
--
Suhail
e on
<https://issues.guix.gnu.org/>.
While "forges" provide both of the above in some form, they may not be
the only way to accomplish the above.
--
Suhail
happen some times when
warranted. Or that,
2. it happens far too rarely today, and should happen more often. Or
that,
3. committers should never ask for revisions?
--
Suhail
ifficulties you
encountered wrt the "current mail-based workflow" are summarized. Is
the difficulty regd. checking out the code at the right commit and
installing the patches, or something else?
--
Suhail
eir email)
- patch *needs followup review* (automatically set if there's a
revised patch)
- patch has a *satisfied reviewer* (set explicitly by the reviewer,
say, by using a specific keyword in their email)
--
Suhail
"Tomas Volf" <~@wolfsden.cz> writes:
> On 2023-11-02 16:38:29 +, Suhail wrote:
>> [..]
>> --
>> Suhail
>>
>> This email is not an offer capable of acceptance, does not evidence an
>> intention to enter into an agreement, has no ope
vailable
quite helpful. In case the intent is to make it easier for newcomers to
the project (i.e., those who've not yet internalized this knowledge) to
contribute, providing such prototypical examples by linking to commits,
descriptions etc in the existing source tree would help.
--
Suhail
This e
s will really help speed up getting things reviewed
> and merged.
Is there a document that outlines how to get started and/or
pre-requisites that one must have before reviewing certain aspects?
--
Suhail
This email is not an offer capable of acceptance, does not evidence an
intention to enter i
"jgart" writes:
> It would create a basic manifest.scm or guix.scm file for the user.
what would the "basic" manifest.scm or guix.scm do? could you share a
sample of what it would look like?
--
Suhail
This email is not an offer capable of acceptance, does not evidenc
-specific, and more generally
"situation-specific", templates
- [optional] allows the appropriate template to be automatically selected
- allows the user to specify the template they desire
cheers
--
Suhail
This email is not an offer capable of acceptance, does not evidence an intention
to
Ludovic Courtès writes:
> The only thing broken for me is completion in shell-mode
FWIW, as an alternative, emacs-bash-completion
(<https://github.com/szermatt/emacs-bash-completion>) works quite well
for completion in shell-mode. I unintern pcomplete/guix and use it in
its stead.
--
Suhail
better than before.
IMO it would help to document the minimal configuration that's needed to
make emacs-guix work as intended. And for this to be testable via some
"guix shell -C" invocation which is also documented.
--
Suhail
23 matches
Mail list logo
