POLL: Upgrading Unpacked Radiant Applications


#1

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.

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?

  2. If you installed Radiant using the gem, did you use the --unpack flag
    with the radiant command?

  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?

The more people who respond the better.


John L.
http://wiseheartdesign.com


#2

On 1/15/07, John W. Long removed_email_address@domain.invalid 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 pole:

  1. Did you install Radiant from source or use the gem?

To create extensions: from source (svn checkout)
To deploy: gem mode

  1. 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.

  1. 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 :slight_smile:


Luis L.
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


#3
  1. Did you install Radiant from source or use the gem?

All installs of radiant that I have performed (both dev and production)
have
been from source.

  1. If you installed Radiant using the gem, did you use the --unpack flag
with the radiant command?
  1. 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 didn’t even know there was support for installing/ upgrading in such a
way. Anything that reduces core development efforts and speeds up
releases
gets a thumbs up from me.

Kev


#4
  1. Did you install Radiant from source or use the gem?
    Source
  1. If you installed Radiant using the gem, did you use the --unpack
    flag
    with the radiant command?
    No.
  1. 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?
    No. I would not mind.

-C


#5
  1. Did you install Radiant from source or use the gem?

Source


#6

On 1/15/07, John W. Long removed_email_address@domain.invalid wrote:

The pole:

  1. Did you install Radiant from source or use the gem?

Source.

  1. If you installed Radiant using the gem, did you use the --unpack flag
    with the radiant command?

n/a

  1. 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?

No, I would not mind. Anything to smooth the release process! I think
people who want an “unpacked” version should just get the source via
download or svn.

*Mars


#7

Quoting “John W. Long” removed_email_address@domain.invalid:

The pole:

  1. Did you install Radiant from source or use the gem?

source

  1. If you installed Radiant using the gem, did you use the --unpack flag
    with the radiant command?

  2. 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?

wouldn’t mind at all - prefer more frequent releases


#8
  1. Source
  2. I’m all for more updates.

BJ Clark


#9

John W. Long wrote:

  1. Did you install Radiant from source or use the gem?

gem

  1. If you installed Radiant using the gem, did you use the --unpack flag
    with the radiant command?

no

  1. 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?

no


#10
  1. Did you install Radiant from source or use the gem?

Gem

  1. If you installed Radiant using the gem, did you use the --unpack flag
    with the radiant command?

Yes – Dreamhost’s ruby server ATM on 2 servers (Confirmed now) does not
respond well to custom-installed gems. I had to unpack radiant and then
had to toss radius into the vendor/ folder to make work properly on
dreamhost. Any suggestions how to correct before I release my tutorial
on how to get the web server’s engine to recognize the personal
installation of gem? Yes, I made .bash_profile and source’d it. Also
made .gemrc. Restarted dispatch.fcgi (Currently running) and won’t pick
up these two gems (Others work) – Yes, I did chmod those as well.

  1. 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 would mind for now just because dreamhost’s gem is goofed. Will work
more on it this weekend to try to make it work to maybe make a better
‘Install your own gems on DreamHost’ tutorial as well. If I could make
it work, I have no problems. :slight_smile:


#11
  1. Gem
  2. No
  3. No

#12

Source / No / No


#13

John W. Long schrieb:

The pole:

  1. Did you install Radiant from source or use the gem?

Gem.

  1. If you installed Radiant using the gem, did you use the --unpack flag
    with the radiant command?

No. Didn’t even know that this flag exists :-/

  1. 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?

The more people who respond the better.

Wouldn’t mind it. More releases? … Great!

Best regards,
Andreas S.


#14

Ditto Giovanni.


#15

Hmmmmm…

Hmmmmm…

(grooming the goatee, now rolling my hypothetical mustage a la
Dali)…err…could we add to the backlog a poll behaviour to
Radiant? (nudge, nudge, wink, wink).


#16

source / no / Would I mind?? Are you kidding? :slight_smile:


#17
  1. Gem
  2. No
  3. No

#18

instance
mode.

I don’t see how folks can use Radiant in instance mode anyway. These
folks don’t add stuff to Radiant at all?

  1. Did you install Radiant from source or use the gem?

Gem.

  1. If you installed Radiant using the gem, did you use the --unpack
    flag
    with the radiant command?

Yes.

  1. 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?

Yes.

Cheers, Joannou.


#19
  1. Did you install Radiant from source or use the gem?

Source

  1. If you installed Radiant using the gem, did you use the --unpack
    flag
    with the radiant command?
  1. 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?

Not at all. More frequent releases would be great. I think it’s
entirely sensible to drop the --unpack luxury if it’s at all costly
to keep.

Loren J.
FN Group
www.fn-group.com


#20

John W. Long 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.

Thanks everyone for the feedback. Sounds like we can drop it. :slight_smile:


John L.
http://wiseheartdesign.com