Ron,

The reason I primarily went to RPM's over the CPAN install option had
more to do with convenience and my limited knowledge than anything else.
When I had issues installing perl mods under CPAN, I never really
understood how to resolve the problem or remove and re-install the
modules. Anyway, sorry to create more work for you and I hope I didn't
sound overly critical of your great work which I will probably use in
the near future.

Eric

On 7/19/2012 9:54 AM, Ron Pacheco wrote:
> Domnick, glad to hear it worked perfectly for you. Eric, yeah, I agree about 
> using RPMs for the perl modules. I'm out of town until late today, but I'll 
> update my script to make that change ASAP when I get back.  --Ron
>
> Sent from my iPad
>
> On Jul 18, 2012, at 11:36 PM, Domnick Eger <[email protected]> wrote:
>
>> I can confirm this works on CentOS 6.2 on XenServer 6.0 it took 35
>> minutes, and I was able to go live as soon as the script finished.
>>
>> I migrated from cents 5.2, and did the backup, and restore took an hour.
>> Perfect setup. Thanks a bunch for that script.
>>
>> On 7/18/12 8:24 PM, "Eric Shubert" <[email protected]> wrote:
>>
>>> Just for the record, using RPMs is the preferred method (instead of
>>> using CPAN), for several reasons that I don't think I need to expound.
>>> RPMs will be used in the 'official' version, so doing so now would be
>>> prudent.
>>> -- 
>>> -Eric 'shubes'
>>>
>>> On 07/18/2012 03:25 PM, Ron Pacheco wrote:
>>>> Oh, actually, looks like I may have interpreted your question backward.
>>>> I suppose it would have been better to find the YUM packages for all the
>>>> perl modules instead of using CPAN, but again, each of those sections
>>>> was taken from code that essentially already did the heavy lifting, I
>>>> simply adapted them to fit into the larger picture, and once it worked,
>>>> I left it alone. That flow chart that starts "Does it work?" and later
>>>> asks "Did you f*** with it?" comes to mind . . . :D
>>>>
>>>> On Wednesday, July 18, 2012 5:21:18 PM, Ron Pacheco wrote:
>>>>> Eric,
>>>>>
>>>>> Fair question. The short answer is that this script evolved as I
>>>>> tackled each install issue in turn, and being partly pieced from other
>>>>> install procedures and partly from my own code, what worked was simply
>>>>> left alone and kept intact. I believe that particular code that pulls
>>>>> those perl modules using YUM was part of one of the original CentOS 5
>>>>> install scripts where I borrowed part of the code from.
>>>>>
>>>>> Ron
>>>>>
>>>>> On Wednesday, July 18, 2012 5:07:14 PM, Eric Broch wrote:
>>>>>> On 7/18/2012 2:03 PM, Ron Pacheco wrote:
>>>>>>> List,
>>>>>>>
>>>>>>> This question appears to come up often enough that a turnkey CentOS
>>>>>>> 6.x installer script is probably worth sharing in its entirety. It is
>>>>>>> available for now via a folder on my company's Box account in both
>>>>>>> 7zip and gzipped tar formats with accompanying MD5 and SHA1 hashes
>>>>>>> (if
>>>>>>> someone has a more appropriate hosting location, let me know):
>>>>>>>
>>>>>>> https://www.box.com/shared/de954e52e0816ffc2e93
>>>>>>>
>>>>>>> This is not officially supported for anyone but myself, but as it can
>>>>>>> make CentOS 6.x installs trivial---I and several colleagues have used
>>>>>>> it without issue---I will try to respond to any queries about it that
>>>>>>> are posted here to this list.
>>>>>>>
>>>>>>> If you plan to use this, read the README thoroughly, and as with any
>>>>>>> unsupported script or software, it is strongly recommended that you
>>>>>>> browse through the script to be sure you understand it before using
>>>>>>> it.
>>>>>>>
>>>>>>> Ron
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail:
>>>>>>> [email protected]
>>>>>>> For additional commands, e-mail:
>>>>>>> [email protected]
>>>>>>>
>>>>>> That looks good, Ron. May I ask one question? Why don't you install
>>>>>> the
>>>>>> perl modules using YUM instead of CPAN as your script installs the
>>>>>> rpmforge repo which maintains these modules?
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>> For additional commands, e-mail:
>>>>>> [email protected]
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail:
>>>>> [email protected]
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to