b2a947e4ba
Those were vague plans for the future and do not relate to missing functionality. It is obvious that we will want to support more implementations in future, as they enter pkgsrc proper. The idea about pkg-config files is similar. Once stuff provides them and other stuff can use them, we will add a variable to locate them. |
||
|---|---|---|
| .. | ||
| haskell | ||
| tests | ||
| DESC | ||
| README | ||
| alsa.mk | ||
| blas.buildlink3.mk | ||
| cargo-binary.mk | ||
| cl-package.mk | ||
| clisp-temp.mk | ||
| cvs-package.mk | ||
| fonts.mk | ||
| fossil-package.mk | ||
| git-package.mk | ||
| haskell.mk | ||
| hg-package.mk | ||
| java-app.mk | ||
| linuxbin.pkg.mk | ||
| love.mk | ||
| luarocks.mk | ||
| pear-channel.mk | ||
| pear-channel.tmpl | ||
| postgresql.mk | ||
| rcd.mk | ||
| svn-package.mk | ||
| wxGTK.mk | ||
| yesno.mk | ||
README
$Id: README,v 1.1 2003/11/28 20:50:02 mpasternak Exp $ Fri Nov 28 21:34:44 CET 2003 This directory is a testbed for new .mk files, that could propably be introduced to pkgsrc/mk/ after testing/development/reviewing/quarantine. Please have in mind, that files you put here must be really well-documented, Doing this you raise the chance the file will be reviewed. The need for their existance must be also important. For settings, that are shared between only a few packages, create "Makefile.common" (see pkgsrc/databases/postgresql for example) -- dotz@irc.pl