Page MenuHomeSolus

Initial inclusion of nanorc

Authored by abdulocracy on Oct 14 2021, 11:26 AM.
Referenced Files
Fri, May 26, 12:52 AM
F10752642: D12019.id29220.diff
Tue, May 16, 3:41 PM
F10752621: D12019.diff
Tue, May 16, 3:37 PM
F10752608: D12019.id30827.diff
Tue, May 16, 3:35 PM
F10752580: D12019.id29193.diff
Tue, May 16, 3:31 PM
F10730750: D12019.diff
Wed, May 10, 11:43 PM
F10725762: D12019.diff
Mon, May 8, 6:33 PM
F10724380: D12019.id29220.diff
Sun, May 7, 3:07 PM



Contains the scopatz nanorc files, new dependency of nano.

Test Plan

Edit .conf file with nano and see if trailing spaces are highlighted green.

Diff Detail

No Lint Coverage
No Test Coverage
Build Status
Buildable 2002
Build 2002: arc lint + arc unit

Event Timeline

JoshStrobl added a subscriber: JoshStrobl.
JoshStrobl added inline comments.

Let's just do: Package with language-specific nanorc files [...]


Use install instead

This revision now requires changes to proceed.Oct 15 2021, 9:40 AM
JoshStrobl added inline comments.

Should be 00644

This revision now requires changes to proceed.Oct 15 2021, 11:27 AM

It's a directory, so 755 I think.

DataDrake added a subscriber: DataDrake.

The name of this package should be nanorc to match the upstream repo.

This revision now requires changes to proceed.Oct 16 2021, 1:17 AM

Should it? Perhaps something like scopatz-nanorc since nanorc by itself is generic. I understand sticking to the upstream name is important but in this case the upstream name isn't really a name.

I don't see how it isn't a name? It's a repo full of nanorc files. Arch is the only distro that currently ships these using that name and I don't agree with their decision.

@DataDrake does raise a good point that nano-syntax-highlighting is not the correct upstream name and we shouldn't be basing our package names around what other operating systems do. nanorc makes sense to me as well.

abdulocracy retitled this revision from Initial inclusion of nano-syntax-highlighting to Initial inclusion of nanorc.Oct 16 2021, 8:35 PM
This revision is now accepted and ready to land.Jan 14 2022, 7:48 PM
This revision was automatically updated to reflect the committed changes.