On 1/15/07, John W. Long <[EMAIL PROTECTED]> wrote: > The core team is looking to revamp the bin/radiant script in the next > release and we are thinking of dropping support for the --unpack flag. >
If user want to unpack a specific gem, he could use gem unpack 'gem name' instead. > The unpack flag extracts the entire source tree from the Radiant gem and > allows you to run the gem in "application" mode rather than "instance" > mode. Presently, it is becoming a pain to create an upgrade script > unpacked Radiant applications, thus we are considering dropping support > for them from the Radiant command. If we did this, you could still > extract Radiant from a tar file to run it in unpacked "application" > mode, but you would be on your own when it comes to upgrading it. > Upgrading would still be supported for applications running in instance > mode. > > The pole: > > 1. Did you install Radiant from source or use the gem? > To create extensions: from source (svn checkout) To deploy: gem mode > 2. If you installed Radiant using the gem, did you use the --unpack flag > with the radiant command? > Even I added that command to the original script, never used it. > 3. Would you mind if we dropped support for upgrading unpacked Radiant > applications (apps installed using the --unpack flag) if it > means that Radiant releases can occur more frequently? > I'm not a Radiant Core developer, but guess maintain the upgrade logic between version is a real pain. > The more people who respond the better. > Hope my comments on this worth something :-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
