This is an old revision of the document!
Topics
Integration with language packages
- languages like Haskell, OCaml, Perl, Python, R, Tex have their own package repositories
- approaches:
- patch to register as FreeBSD pkg
- e.g. scrape each CTAN directory
- pkg plugin to resolve new kinds of dependences (which can query language package system)
- e.g. when requesting a tex package, go to CTAN
- it would be difficult to depend on e.g. texlive-2013
- could integrate using Provides: ?
- this would require a solver that can integrate with external repositories
- pkg 1.2 will have a pluggable solver that might support this
- pkg uses CUDF (sp?); could feed everything using this?
- lots of work: different systems provide different information, name packages differently…
- rwatson covers eyes when word “ontology” is mentioned
- principle: the ports tree is one way of creating packages
- base is another possible source
- Adrian: in the new world, how do I patch upstream's packages?
- bapt: create a port
- funky new pkgng goodness
- can build packages from CMake, hopefully autotools soon
- pkgng can scan packages you build, look for e.g. library dependencies and the packages they come from
- could end up with multiple repositories (ports, Perl, Python…)
- do we build repositories or just register installed language packages?
- brooks: could replace the language packaging systems' implementations
- gabor: it's not a good idea to follow upstream blindly
- some complexity is unavoidable when maintaining a package repository
- brooks: is anybody planning on actually implementing one of these?