Closed JasonJAyalaP closed 6 years ago
Those are all great tips, we could improve docs across the board thanks.
The difference from brew is that everything is a self contained package so you can just download a .pkg from rudix and be done with it. No recompilation in thousands of machines of the same code, no dependencies to care about.
Starting a new port is easy, just fork the repo, add your directory on the right place and use a makefile for guidance (we really need more docs about this). Usually the default steps download sources from upstream, build them (trying to statically link depencies) to a prefix directory (/usr/local IIRC) and them package the resulting data in a pkg... all without messing with your computer.
And once I create the makefile, how do I test it?
The packages are built and stored on a rudix server?
@JasonJAyalaP , I usually build the packages in my Machine (on a bunch of VMs), so it's OK to build on your machine, there is no test grid ou build grid. The packages are stored in Rudix Server, which I maintain, the packages are uploaded manually by me, so I would not use your package, but I build for my on own and then upload. So I bulld packages for Mavericks, Mountain Lion, Lion and Snow Leopard.
If you're having trouble, we can schedule a Hangout or a session on IRC. Thanks!
The website talks about using the native pkg functions of OSX. Rudix installs to / and keeps track of the install files like RPM/Deb? The website could talk about how this is superior to homebrew's concept of keeping everything in Cellar/ + symlinks.
A comparison to brew/macports/fink/nix is necessary, I think.
I tried to find out how to build packages. I'm guessing from github/documentation/makefile, I fork the repo, edit a makefile using the example, and make a pull request? The github README could explain this.
Are the binary tar.gz files, which the makefile points to, expected to extract cleanly to / ? Are there any special functions for more complicated tarballs?