this post was submitted on 23 Aug 2024
447 points (94.6% liked)

linuxmemes

21197 readers
70 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    447
    My impression of github since switching to Linux (lemmy.world)
    submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]
    121 comments fedilink hide all child comments
     

    I've been transitioning to Linux recently and have been forced to use github a lot when I hadn't much before. Here is my assessment.

    Every github project is named something like dbutils, Jason's cool photo picker, or jibbly, and was forked from an abandoned project called EHT-sh (acronym meaning unknown) originally made by frederick lumberg, forked and owned by boops_snoops and actively maintained by Xxweeb-lord69xX.

    There are either 3 lines of documentation and no releases page, or a 15 page long readme with weekly releases for the last 15 years and nothing in between. It is either for linux, windows, or both. If it's for windows, they will not specify what platforms it runs on. If it's for Linux, there's a 50% chance there are no releases and 2 lines of commands showing how to build it (which doesn't work on your distro), but don't worry because your distro has it prepackaged 1 version out of date and it magically appears on flatpak only after you've installed it by other means. Everything is written in python2. It is illegal to release anything for Mac OS on github.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 14 points 2 months ago (1 children)

    You're doing "Bob's" work son, thank you for your service!

    As a devout SubGenius myself it is my destiny to use Slackware one day but alas I fear it is currently above my skill level, more documentation will help people like me greatly! PRABOB!

    1000003261

    [–] [email protected] 5 points 2 months ago (1 children)

    It's easier to install and administer than Arch, and won't break on updates.
    But yeah, the current state of the documentation is discouraging.

    [–] [email protected] 1 points 2 months ago (1 children)

    I'm more worried about package management I guess. Though I suppose now with flatpak that may be less of an issue. Still I use some weird shit, some of it is only packaged as a .deb or .rpm on their site, like the Brother printer drivers.

    And yeah the documentation lol. I rely heavily on that or places like lemmy for linux help, which is why to start I picked a really popular distro with good documentation (fedora). It's definitely something I'll try one day though!

    [–] [email protected] 4 points 2 months ago* (last edited 2 months ago) (1 children)

    You can have a look at slackbuilds.org to see if what you need is available. It's Slackware's AUR equivalent.
    You can install packages from there using sbopkg, which does handle dependencies.

    It does have the Brother drivers: https://slackbuilds.org/repository/15.0/system/brlaser/

    Up-to-date documentation comes in the form of easy to understand text files written by Pat himself, that are installed with the distro. For questions, linuxquestions.org is the place to go. The main devs of the distro read and post there regularly.
    That's also what I love about Slackware. I wrote one of the main devs an e-mail and got a helpful, friendly reply half an hour later. That's what Linux used to be like.

    [–] [email protected] 2 points 2 months ago

    Thanks! This inspires confidence! Seems like it won't be so bad!