Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Would it make sense to mark known to be broken packages in the packages list?

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    4 Posts 3 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • rcfaR
      rcfa
      last edited by

      There are a variety of packages in the available packages list that are known to be busted, e.g. stunnel

      It's rather easy to screw up a setup by installing a broken package, so it might be useful to have some sort of warning when a package is known to be busted.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Kind of a catch-22 there. If we disable them, there's no way for someone to install and troubleshoot/debug them. Also they may work for some people and not others, or they may work for people who are willing to take extra manual steps before they work.

        It might be good to change their status to "Possibly Broken" but someone would still need to pay attention to that field for it to be effective.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • rcfaR
          rcfa
          last edited by

          @jimp:

          Kind of a catch-22 there. If we disable them, there's no way for someone to install and troubleshoot/debug them. Also they may work for some people and not others, or they may work for people who are willing to take extra manual steps before they work.

          It might be good to change their status to "Possibly Broken" but someone would still need to pay attention to that field for it to be effective.

          Right, that's why I said "mark" not "disable" or "hide". Basically, anything that alerts a user that they are entering potentially troubled territory would be good. At that point one can peruse the forums to see why things are marked, and decide if one wants to proceed or not.

          e.g. vhosts works fine, it just doesn't display properly on the dashboard.
          Other things are more dangerous.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            If something is completely and totally broken, it should be disabled. I'm not aware of any packages currently that are completely broken. General stability of packages is noted by their status: alpha, beta, stable.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.