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

    Bsd pkg sync

    Scheduled Pinned Locked Moved 2.3.1 Snapshots Testing and Feedback - ARCHIVED
    6 Posts 4 Posters 3.2k 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.
    • P
      paftdunk
      last edited by

      As of 2.3 we can only install whitelisted packages, out of concern with conflicts. If pfSense is going to maintain a private curated repo, how about publishing the entire FreeBSD 10.3 set minus whatever is bundled with pfSense itself? It seems like that would be a lot less effort and inconvenience than the piecemeal approach that seems to be the plan right now.

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

        That's more because poudriere doesn't have a "build everything except this" feature. It's something we've already discussed internally. Though even if there were, there are more ports that aren't applicable than those that are. There are a lot of big packages that have no applicability in our use case (all desktop-related things, X11, office suites, etc.), among potentially a wide range of others.

        I'm open to adding anything that's reasonable for our use cases and won't conflict. I've been adding things people suggest and will continue to do so.

        1 Reply Last reply Reply Quote 0
        • P
          paftdunk
          last edited by

          Thanks for the reply. I didn't realize it required actually building, as opposed to just pulling in the package, or even redirecting to the upstream port. If the latter two were possible, then the irrelevance of most packages wouldn't really matter as much.

          1 Reply Last reply Reply Quote 0
          • K
            kpa
            last edited by

            You have to build everything yourself if you're going to offer your own binary package repository, there's no way around it at the moment because mixing multiple pkg repositories is not really working yet as intended.

            1 Reply Last reply Reply Quote 0
            • S
              shaqan
              last edited by

              @cmb:

              I'm open to adding anything that's reasonable for our use cases and won't conflict. I've been adding things people suggest and will continue to do so.

              perhaps nano? Shouldn't have many dependencies and it's flat out easier to use for novice than vi.

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

                nano's been there for a while.

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