Really?

Discussion in 'General Discussion' started by dinsdale, Nov 24, 2015.

  1. dinsdale

    dinsdale Member

    Joined:
    Oct 22, 2015
    Messages:
    23
    Likes Received:
    13
    So, I'm just kinda geeking out here about using pkgng as the OS update engine. That would mean technically D2BSD could start the entire installation process using bmake (and the mk directory), clang, curl and the ports tree.

    Really?
     
  2. malco_2001

    malco_2001 DesktopBSD Veteran

    Joined:
    Feb 22, 2015
    Messages:
    50
    Likes Received:
    14
    Yes. I have been playing around with the projects/release-pkg branch of FreeBSD for this in the future. Here is what the packages look like so far:

    FreeBSD-acpi-11.0.s20151127084927.txz
    FreeBSD-at-11.0.s20151127084927.txz
    FreeBSD-bhyve-11.0.s20151127084927.txz
    FreeBSD-binutils-11.0.s20151127084927.txz
    FreeBSD-bsdinstall-11.0.s20151127084927.txz
    FreeBSD-bsnmp-11.0.s20151127084927.txz
    FreeBSD-bsnmp-development-11.0.s20151127084927.txz
    FreeBSD-bsnmp-lib32-11.0.s20151127084927.txz
    FreeBSD-bsnmp-lib32-development-11.0.s20151127084927.txz
    FreeBSD-bsnmp-lib32-profile-11.0.s20151127084927.txz
    FreeBSD-bsnmp-profile-11.0.s20151127084927.txz
    FreeBSD-clang-11.0.s20151127084927.txz
    FreeBSD-development-11.0.s20151127084927.txz
    FreeBSD-dma-11.0.s20151127084927.txz
    FreeBSD-docs-11.0.s20151127084927.txz
    FreeBSD-gdb-11.0.s20151127084927.txz
    FreeBSD-groff-11.0.s20151127084927.txz
    FreeBSD-lib32-11.0.s20151127084927.txz
    FreeBSD-lib32-development-11.0.s20151127084927.txz
    FreeBSD-lib32-profile-11.0.s20151127084927.txz
    FreeBSD-profile-11.0.s20151127084927.txz
    FreeBSD-runtime-11.0.s20151127084927.txz
    FreeBSD-ssh-11.0.s20151127084927.txz
    FreeBSD-ssh-development-11.0.s20151127084927.txz
    FreeBSD-ssh-lib32-11.0.s20151127084927.txz
    FreeBSD-ssh-lib32-development-11.0.s20151127084927.txz
    FreeBSD-ssh-lib32-profile-11.0.s20151127084927.txz
    FreeBSD-ssh-profile-11.0.s20151127084927.txz
    FreeBSD-svn-11.0.s20151127084927.txz
    FreeBSD-syscons-11.0.s20151127084927.txz
    FreeBSD-tests-11.0.s20151127084927.txz
    FreeBSD-unbound-11.0.s20151127084927.txz
    FreeBSD-unbound-development-11.0.s20151127084927.txz
    FreeBSD-unbound-lib32-11.0.s20151127084927.txz
    FreeBSD-unbound-lib32-development-11.0.s20151127084927.txz
    FreeBSD-unbound-lib32-profile-11.0.s20151127084927.txz
    FreeBSD-unbound-profile-11.0.s20151127084927.txz
     
  3. dinsdale

    dinsdale Member

    Joined:
    Oct 22, 2015
    Messages:
    23
    Likes Received:
    13
    What's the reason for the *-developer* packages? Super cool though. I'll dig into that later. Need to figure out launchd scripts right now.
     
  4. malco_2001

    malco_2001 DesktopBSD Veteran

    Joined:
    Feb 22, 2015
    Messages:
    50
    Likes Received:
    14
    Not sure. I'm still digging in myself. I would guess the developer packages are probably the source code required for other programs to build around libraries.