Permalink
Browse files

Convert site to github pages

  • Loading branch information...
1 parent e2e79f6 commit 592017d2cf82db6de9a1b7404ea93cec7d1e9d51 @leto committed Jul 24, 2011
Showing with 0 additions and 5,335 deletions.
  1. +0 −46 CREDITS
  2. +0 −70 HACKING.git
  3. +0 −7 HACKING.parrot
  4. +0 −34 HACKING.postgres
  5. +0 −19 HISTORY
  6. +0 −83 IDEAS
  7. +0 −201 LICENSE
  8. +0 −53 META.json
  9. +0 −70 Makefile
  10. +0 −10 PLATFORMS
  11. BIN {html → }/PLParrot_PGCon_2010.pdf
  12. BIN {html → }/PLParrot_SFPM_20100525.pdf
  13. +0 −114 README.md
  14. +0 −39 ROADMAP
  15. +0 −23 TODO
  16. +0 −105 bin/text2macro.pl
  17. 0 {html → }/community.html
  18. +0 −2 config.h
  19. 0 {html → }/css/project-site.css
  20. 0 {html → }/docs.html
  21. +0 −41 expected/test.out
  22. BIN {html → }/img/PLParrot.jpg
  23. 0 {html → }/index.html
  24. 0 libsrc/handler/.placeholder
  25. +0 −23 load_pir.test.sql
  26. +0 −1,539 pgtap.sql
  27. +0 −599 plparrot.c
  28. +0 −41 plparrot.sql.in
  29. +0 −49 plparrot_secure.pir
  30. 0 {html → }/plperl6.html
  31. +0 −65 plperl6.pir
  32. 0 {html → }/plpir.html
  33. +0 −6 ports/debian/README.Debian
  34. +0 −9 ports/debian/README.source
  35. +0 −5 ports/debian/changelog
  36. +0 −1 ports/debian/compat
  37. +0 −21 ports/debian/control
  38. +0 −219 ports/debian/copyright
  39. +0 −4 ports/debian/cron.d.ex
  40. +0 −2 ports/debian/docs
  41. +0 −45 ports/debian/emacsen-install.ex
  42. +0 −15 ports/debian/emacsen-remove.ex
  43. +0 −25 ports/debian/emacsen-startup.ex
  44. +0 −157 ports/debian/init.d.ex
  45. +0 −296 ports/debian/init.d.lsb.ex
  46. +0 −59 ports/debian/manpage.1.ex
  47. +0 −154 ports/debian/manpage.sgml.ex
  48. +0 −291 ports/debian/manpage.xml.ex
  49. +0 −2 ports/debian/menu.ex
  50. +0 −2 ports/debian/plparrot-dev.dirs
  51. +0 −6 ports/debian/plparrot-dev.install
  52. +0 −10 ports/debian/plparrot.default.ex
  53. +0 −20 ports/debian/plparrot.doc-base.EX
  54. +0 −1 ports/debian/plparrot1.dirs
  55. +0 −1 ports/debian/plparrot1.install
  56. +0 −39 ports/debian/postinst.ex
  57. +0 −37 ports/debian/postrm.ex
  58. +0 −35 ports/debian/preinst.ex
  59. +0 −38 ports/debian/prerm.ex
  60. +0 −13 ports/debian/rules
  61. +0 −1 ports/debian/shlibs.local.ex
  62. +0 −23 ports/debian/watch.ex
  63. +0 −62 ports/fedora/postgresql-plparrot.spec
  64. +0 −1 sql
  65. +0 −206 t/sql/plperl6.sql
  66. +0 −296 t/sql/test.sql
  67. 0 {html → }/template.html
View
46 CREDITS
@@ -1,46 +0,0 @@
-=pod
-
- Following in the steps of other open source projects that
- eventually take over the world, here is the partial list
- of people who have contributed to PL/Parrot and its supporting
- works. It is sorted by name and formatted to allow easy
- grepping and beautification by scripts.
- The fields are: name (N), email (E), web-address (W),
- description (D), main username (U), alias usernames (A)
- and snail-mail address (S).
-
- Thanks,
-
- The PL/Parrot Team
- PS: Yes, this looks remarkably like the Linux CREDITS format
- PPS: This file is encoded in UTF-8
-
-----------
-
-N: Jonathan Leto
-E: jonathan@leto.net
-W: http://leto.net
-U: dukeleto
-S: Portland, OR
-
-N: David Fetter
-E: david@fetter.org
-W: http://www.pgexperts.com/
-U: davidfetter
-S: Oakland, CA, USA
-
-N: David Wheeler
-E: david.wheeler@pgexperts.com
-W: http://www.pgexperts.com/
-U: theory
-S: Portland, OR, USA
-
-N: Joshua Tolley
-E: eggyknap@gmail.com
-W: http://eggyknap.blogspot.com
-U: eggyknap
-S: Salt Lake City, UT, USA
-
-N: Daniel Arbelo Arrocha
-E: arbelo@gmail.com
-U: darbelo
View
@@ -1,70 +0,0 @@
-=head1 Recommended Git Workflow for Working on PL/Parrot
-
-You should be using Git >= 1.6.x . Make sure you do before doing anything in this file.
-
-=head1 Workflow #1 (used by dukeleto)
-
- git remote update # this updates your index and the symbolic ref origin/master
-
-The benefit of this way is that "git remote update" only updates your index and doesn't care
-about changes in your working copy i.e. you can have a messy, uncommited pig sty in your local
-copy and remote update just doesn't care.
-
- git diff ..origin/master # look at the difference between local master and origin/master
-
-This shows commits which are in origin/master but not in master.
-
-If you want an colored ASCII representation of your history (also known as VCS porn):
-
- git log --pretty=format:'%C(yellow)%h%Creset %s %Cred%an%Creset %Cblue%d%Creset %Cgreen%cr%Creset %cd' --graph --all
-
-I have this aliased to both "git lg" for "log --graph" and "git plog" for "pretty log". For other useful aliases, see
-
-http://github.com/leto/Util/blob/master/config/.gitconfig
-
-If you want to merge the changes from origin/master into your local master:
-
- git rebase origin/master
-
-Why not just a merge? That would leave a "merged branch 'master'" commit, which
-gets old real quick. We also spam the #parrot channel with our commits, so it
-is best to not have all those (mostly useless) merge commits.
-
-=head1 Workflow #2 (pretty much equivalent, but less flexible)
-
-Something equivalent to the above can be accomplished with:
-
- git pull --rebase # same as git rebase
-
-but this command *does* care about having a clean working copy, so if you have uncommitted changes, you
-will have to stash them:
-
- git stash "this is a work in progress"
-
-This command will leave you with a clean working copy, so that after you type "git pull --rebase" you can type:
-
- git stash pop # apply the latest commit on the stash and pop it off
-
-You could have used "git stash apply" if you wanted to apply it but leave it on
-the stash. You might want to do this if you want to apply something to multiple
-branches.
-
-If you want to type "git pull" and you always want it to use --rebase then you can do:
-
- git config branch.master.rebase true
-
-I think it is better to just use "git rebase", so if you type "git pull" it
-does what you expect, but that is up to personal taste.
-
-=head1 How to Write a Commit Message
-
-Commit messages should look like this:
-
-This is the first line, which is roughly 50 columns, no more than 80
-
-Previous line intentionally left blank! That line separates the short commit
-message from the long commit message. Utils that need to print things on one
-line will use the short commit messages, others that don't care will show the
-long commit message.
-
-=cut
View
@@ -1,7 +0,0 @@
-Here's a way to have fresh parrots.
-
-Figure out what to put in instead of -j4 by figuring out how many
-cores are available. On Linux, you can cat /proc/cpuinfo.
-
-export PATH=$HOME/installed_parrot/bin:$PATH
-alias new_parrot="make realclean; perl Configure.pl --optimize --prefix=$HOME/installed_parrot && nice -n20 gmake -j4"
View
@@ -1,34 +0,0 @@
-PostgreSQL depends on some environment variables and directories which
-are easiest to have via a .bashrc like this:
-
-export PG_PREFIX=/home/shackle/tip
-export PGDATA=$PG_PREFIX/data
-export PATH=$PG_PREFIX/bin:$PATH
-export PGPORT=2225
-export PGUSER=shackle
-export PGDATABASE=postgres
-
-When you want to work on CVS TIP (aka git master) of PostgreSQL, you'd
-source this file first. If you want to change to another
-PostgreSQL, do:
-
- make maintainer-clean
- . /path/to/new/.bashrc.whatever
-
-When compiling PostgreSQL, here's a handy-ish configure invocation:
-
- ./configure \
- --prefix=$PG_PREFIX \
- --with-pgport=$PGPORT \
- --with-perl \
- --with-libxml \
- --enable-debug \
- --enable-cassert
-
-If you have ccache installed, you may also want to do
-
- CC="ccache gcc" ./configure ...
-
-To avoid confusion, you also might want to un-symlink plparrot from
-beneath the other source tree and symlink it under contrib/ in the
-source tree you want to use.
View
19 HISTORY
@@ -1,19 +0,0 @@
-David Fetter recounts:
-
-As has long been my wont, in about May of 2006, I was looking around for
-something cool to do in PostgreSQL that no one had done before. I figured
-perl6 would make a great PL, but there was no implementation at the time, or at
-least nothing that looked like it might become embeddable Parrot, despite its
-long ride on the fail whale, looked like the most promising way for the long
-term, So i came up with a couple of designs inspired by the PL/Java and PL/J
-projects. PL/Java produced working code, although to this day I'm not sure
-that it's production quality. It did this by instantiating a jvm in each
-connection. PL/J's design was in some sense more elegant, but it never got
-anywhere. In PL/J, there was to be some kind of IPC to a java "server." The
-problem is that IPC and little servers are extremely difficult to get right, so
-for now, I'm thinking that the PL/Java model has more JFDI.
-
-Jonathan "Duke" Leto adds:
-
-I started hacking on PL/Parrot in October of 2009 and it started to actually work
-in April 2010.
View
83 IDEAS
@@ -1,83 +0,0 @@
-
-Ways to get Parrot in your Postgres database:
-
-* Embedd One VM per postgres backend
- ** load via a shared library (.so or .dylib)
-* pure NCI
-
-Notes for the PostgreSQL side:
-
-* PL/LOLCODE http://pgfoundry.org/projects/pllolcode/
-
-* http://www.postgresql.org/docs/8.4/static/xfunc-c.html
-
-* http://www.postgresql.org/docs/8.4/static/plhandler.html
-
-* http://developer.postgresql.org/pgdocs/postgres/parser-stage.html
-
-* http://www.postgresonline.com/journal/index.php?/archives/6-Language-Architecture-in-PostgreSQL.html
-
-Notes for the Parrot side:
-
-* mod_parrot http://www.parrot.org/mod_parrot
-
-* Parrot Core Embedding Docs: http://docs.parrot.org/parrot/latest/html/docs/pdds/draft/pdd10_embedding.pod.html
-
-Other random semi-related stuff
-
-* PL/R http://www.joeconway.com/plr/
-
-* PL/Scheme http://plscheme.projects.postgresql.org/
-
-* R in Postgres: http://www.omegahat.org/RSPostgres/
-
-Things we'll need to build:
-1) A C-based shared object containing at minimum a "language handler" function.
-This is what PostgreSQL calls when trying to execute a PL/Parrot function, and
-it's responsible for invoking the interpreter. This will probably be called
-plparrot.so
-
-2) Some sort of module PL/Parrot functions can import which will allow them to
-talk to the database.
-
-There will be some interesting interaction, perhaps, between these two modules.
-The handler function is the only one that will have capacity to talk to the
-database (barring opening a new connection to the database from Parrot, but
-that would obviate the benefits of a procedural language). Presumably the .so
-will need to export functions to the module to allow it to get to the database.
-
-The first step in all this is to get the handler function working, so you can
-run Parrot routines that don't access the database, you can pass them data, and
-they can return data. Second will be to make the database interaction module
-work.
-
-Update:
-01:54 eggyknap : So presumably we can write, in nqp-rx, something that can export some functions and be loaded by any function written in a
- language parrot understands... and presumably those exported functions can actually wrap C code we'll write in the C bits
- of pl/parrot?
-01:54 dukeleto : eggyknap: that sounds about right
-01:55 dukeleto : eggyknap: please write that down somewhere :)
-01:55 eggyknap : Sweet... 'cuz that's how it's gotta work, AFAICS.
-
-
-David Wheeler suggests shelling out directly to psql from the test harness instead of using pg_prove. Fewer dependencies!
-
-This is how the pgTAP plugin for Test::Harness does it:
-http://github.com/AndyA/Test-Harness/blob/master/lib/TAP/Parser/SourceHandler/pgTAP.pm
-
-psql
- --no-psqlrc
- --no-align
- --quiet
- --pset pager=
- --pset tuples_only=true
- --set ON_ERROR_ROLLBACK=1
- --set ON_ERROR_STOP=1
-
-
-IDEAS FOR EXPOSING POSTGRES FUNCTIONS IN PL/PARROT
-* At minimum we need to expose a set of functions: elog(), and SPI stuff, and possibly even utility functions to get pieces of PostgreSQL data types that might not map cleanly to Parrot HLLs
-* One possibility is to create a PMC that people use to access PostgreSQL. This PMC would include methods corresponding to each of the functions we need to expose
- ** Update: per dukeleto this idea won't fly -- PMCs only have some functions available, not a set of arbitrary function names. http://docs.parrot.org/parrot/devel/html/docs/pdds/pdd17_pmc.pod.html
-* Alternatively we can just make the functions available somehow. The primary advantage of PMC over this method as I (eggyknap) see it, is that it seems easier to figure out how to write a PMC than to figure out how to make functions magically available in PL/Parrot functions
- ** Good place to look for examples: runtime/parrot/library/OpenGL.pir
Oops, something went wrong.

0 comments on commit 592017d

Please sign in to comment.