- Suggestion of a base set of packages to provide security fixes.
- theraven suggests branching will help with security fixes.
- bapt says we'll look at this after we have some experience with pkg sets.
- proposal for large scale renaming and splitting of ports categories to make it easier for users to find things
- Significant costs associated with moving most packages in svn
- discussion of alternative metadata to provide similar views
- discussion of issues of naming packages in a work without categories
- Further discussion of how to deal with things like llvm and subversion that have multiple versions
ports with clang and libc++
- Things largely work with clang, mostly ignoring CC, CXX, etc
- No exp run yet for libc++. Cross threading of C++ std libraries will often be a problem that we're already hitting with gcc46.
provides / requires
- implemented in next version of pkgng
- Ports declare things like: "I provide an http server" or "I need a web server with php"
Allow ports to depend on either libjpeg or libjpegturbo, on perl > 5.12, etc
- Jonathan raises the issue of C++ libraries with/without RTTI
- Flavors suggested as a solution, but not clear everything required is supported
- Forcing rpaths or adding per-port /usr/local/etc/libmap.d (coming to HEAD soon) or similar
cross building ports
- bapt says: pkgsrc cross build mostly don't work
- sson's qemu-usermode is the future. mips64 working, arm nearly there.
compiler selection infrastructure
- Allow user to pick their favorite default compiler
- Porter should be able to specify the supported compiler(s) for their port
- Brooks requests the ability to specify an external compiler as the default ports compiler
- bapt says we could add the compiler used as a package annotation so we can examine that in a pkg set.
- New solver requires a new INDEX format
- A format should be quickly and incrementally updatable with data from OPTIONS changes.
- One suggestion is using the pkg repo format
keywords for plist
- pkg supports all old @keyword values
- Deprecates @exec and @unexec
Centralized keywords stored in YAML format in /usr/ports/Keywords/keyword.yaml
- Lots of discussion about when the keywords should be expanded
- Adding users is a specific example of something the packager can't actually know how to do this for a given system.
- required for sub-packages
supports -R /root/path
ports as user
- Good idea. Someone should work on this. (Staging directory required)
- SAT solver for "requires" support
- Support arguments to ssh to allow multiple administrators to access a shared repo
- support for command aliases
killing shell scripts
- They should die. Keywords are on the path there.