On Mon, Oct 09, 2023 at 01:17:10PM -0400, Maxim Cournoyer wrote:
> Hi,
>
> "jgart" writes:
>
> >> You want `info -f doc/guix.info`.
> >
> > Ah yes, I actually used that flag once before and had forgotten it...
>
> FWIW, it works for me even without '-f'.
To add in some more similar and useful
Hi,
"jgart" writes:
>> You want `info -f doc/guix.info`.
>
> Ah yes, I actually used that flag once before and had forgotten it...
FWIW, it works for me even without '-f'.
--
Thanks,
Maxim
> You want `info -f doc/guix.info`.
Ah yes, I actually used that flag once before and had forgotten it...
Thanks!
Hi jgart,
> Is there a way to open the guix manual directly?
>
> Not sure why info opens a "main page" with all my texinfo manuals when
> I give it doc/guix.info as an argument... 閭
You want `info -f doc/guix.info`.
HTH,
--
Josselin Poiret
signature.asc
Description: PGP signature
Hi,
"jgart" writes:
>> 'make'), and you can review the new work with 'info doc/guix.info'.
>
> Hi,
>
> Is there a way to open the guix manual directly?
Did you try it? It works for me. Or just 'info guix' to open the Guix
manual from found from INFOPATH.
--
Thanks,
Maxim
Hi,
El 8/10/23 a las 13:11, jgart escribió:
Doing info texinfo is TMI:
https://up.nixnet.services/7tzldvyw.png
According to the Guix manual
(https://guix.gnu.org/es/manual/devel/en/html_node/Writing-Documentation.html),
people is encouraged to contribute documentation in any format.
So
> 'make'), and you can review the new work with 'info doc/guix.info'.
Hi,
Is there a way to open the guix manual directly?
Not sure why info opens a "main page" with all my texinfo manuals when I give
it doc/guix.info as an argument... 閭
https://up.nixnet.services/89q7q1f9.png
Hi,
Munyoki Kilyungi writes:
> Hi Maxim!
>
> Maxim Cournoyer
> aliandika:
>
>> Hi,
>>
>> Munyoki Kilyungi writes:
>>
>>> "jgart" aliandika:
>>>
Hi Guixers,
I was recently reviewing a patch by a contributor and was discussing the
notion of preferring upstream to PyPI when
Hi,
Munyoki Kilyungi writes:
> "jgart" aliandika:
>
>>> Sometimes, PyPI versions lag behind upstream versions.
>>
>> Hi Bonz,
>>
>> Yes, in my experience that has sometimes been the case because maintainers
>> don't make timely releases to PyPI.
>>
>>> What's the policy on this. Shouldn't we
Hi Maxim!
Maxim Cournoyer
aliandika:
> Hi,
>
> Munyoki Kilyungi writes:
>
>> "jgart" aliandika:
>>
>>> Hi Guixers,
>>>
>>> I was recently reviewing a patch by a contributor and was discussing the
>>> notion of preferring upstream to PyPI when tests are missing on PyPI.
>>>
>> What's the
Hi,
Munyoki Kilyungi writes:
> "jgart" aliandika:
>
>> Hi Guixers,
>>
>> I was recently reviewing a patch by a contributor and was discussing the
>> notion of preferring upstream to PyPI when tests are missing on PyPI.
>>
> What's the policy on this. Shouldn't we prefer
> upstream over PyPI?
"jgart" aliandika:
>> Sometimes, PyPI versions lag behind upstream versions.
>
> Hi Bonz,
>
> Yes, in my experience that has sometimes been the case because maintainers
> don't make timely releases to PyPI.
>
>> What's the policy on this. Shouldn't we prefer upstream over PyPI?
>
> Our
> Sometimes, PyPI versions lag behind upstream versions.
Hi Bonz,
Yes, in my experience that has sometimes been the case because maintainers
don't make timely releases to PyPI.
> What's the policy on this. Shouldn't we prefer upstream over PyPI?
Our importer works with the JSON API that PyPI
"jgart" aliandika:
> Hi Guixers,
>
> I was recently reviewing a patch by a contributor and was discussing the
> notion of preferring upstream to PyPI when tests are missing on PyPI.
>
What's the policy on this. Shouldn't we prefer
upstream over PyPI? Sometimes, PyPI versions lag
behind
Hi Guixers,
I was recently reviewing a patch by a contributor and was discussing the notion
of preferring upstream to PyPI when tests are missing on PyPI.
WDYT if we also signalled a special condition when there are missing tests in
PyPI?
I'm thinking of something similar to here:
15 matches
Mail list logo
