Skip to content

Conversation

@EbonJaeger
Copy link
Member

Summary

We've always done this thing where the colons in package.yml files were aligned; but only the top-level ones. While it arguably looks nicer (I personally disagree), it also makes it really hard to work with other YAML tooling, such as formatters. It also kept us from being able to automatically sort dependencies. Let's do away with it, unlocking us to use more standard tools.

Test Plan

  1. virtualenv venv
  2. source venv/activate.fish
  3. pip install .
  4. ybump ~/repos/getsolus/solus-packages/packages/n/nano/package.yml

We've always done this thing where the colons in `package.yml` files
were aligned; but only the top-level ones. While it arguably looks nicer
(I personally disagree), it also makes it really hard to work with other
YAML tooling, such as formatters. It also kept us from being able to
automatically sort dependencies. Let's do away with it, unlocking us to
use more standard tools.

Signed-off-by: Evan Maddock <[email protected]>
@EbonJaeger EbonJaeger force-pushed the no-more-weird-colon-things branch from ce41540 to 595206d Compare December 8, 2025 21:20
Copy link
Member

@sheepman4267 sheepman4267 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does what it says on the tin. This should be merged and deployed before the mass conversion of package files.

@ReillyBrogan
Copy link
Contributor

1000 thumbs up from me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants