[jifty-devel] Now available, a shipwright build of Jifty.

[Stanislav Sinyagin]

looks interesting. How do you handle different OS'es default paths? 
For example, blastwave.org, a packaging system for Solaris, installs everything inside /opt/csw.

I'll try someday to use Shipwright together with Torrus (torrus.org): in order to utilize
multithreading, one has to upgrade the "threads" and "threads::shared" packages, because the ones
that come with Perl contain several severe bugs. Then it's a pain if you want to package Torrus 
for any OS: packaging systems refuse to manage files belonging to Perl main package.

By the way, did anyone try using Jifty in Perl multithreaded environment?

chers,
stan


----- Original Message ----
From: Jesse Vincent <jesse at bestpractical.com>
To: Nifty apps in a Jiffy <jifty-devel at lists.jifty.org>
Sent: Thursday, February 14, 2008 10:46:34 PM
Subject: [jifty-devel] Now available, a shipwright build of Jifty.


Five 
lines 
to 
go 
from 
zero 
to 
a 
running 
Jifty:


svn 
co 
http://code.bestpractical.com/shipwright/jifty/ 
jifty-builder
cd 
jifty-builder
./bin/shipwright-builder  
# 
optionally 
--skip-perl 
--skip 
test
cp 
-rvp 
/tmp/jifty-$random/jifty 
/usr/local/jifty
ln 
-s 
/usr/local/jifty/bin/jifty 
/usr/local/bin/jifty


A 
little 
bit 
about 
Shipwright, 
our 
new 
code 
packaging 
tool

Like 
any 
opensource 
software 
shop, 
we 
distribute 
the 
source 
code
for 
our 
software. 
How's 
that 
for 
the 
obvious 
statement 
of 
the 
decade?




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jifty.org/pipermail/jifty-devel/attachments/20080215/9c673ee4/attachment.htm