[ 
https://issues.apache.org/jira/browse/WHIRR-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439916#comment-13439916
 ] 

Paul Baclace commented on WHIRR-562:
------------------------------------

I want this; I need to do a workaround in 0.8.0.

Correction to description (I think):  the function scripts use $REPO_HOST not 
$REPO 

The os_arch makes a difference too, so the approach here can handle anything 
without complex factoring (amd64 is used by the cloudera repo for CDH4, but 
x86_64 is reported by lsb_release.)

FYI:  My workaround to use 12.04 precise:
1.  copy any *.sh files that contain "deb-src" and "cdh" to 
$WHIRR_HOME/functions (a newly created directory for overrides)

2. Use the following to obtain CDH4 for precise:


deb [arch=amd64] http://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh 
precise-cdh4 contrib
deb-src [arch=amd64] http://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh 
precise-cdh4 contrib

NOTE that the 'precise' vs. 'lucid' part could come from (lsb_release -s -c) 
run in the script itself, but I have no idea how portable that is.

WHIRR-573 is related and committed, but did not achieve full factorization (as 
described in a comment). 


                
> [deb specific] Allow specifying the distribution entirely in the 
> cloudera.list file.
> ------------------------------------------------------------------------------------
>
>                 Key: WHIRR-562
>                 URL: https://issues.apache.org/jira/browse/WHIRR-562
>             Project: Whirr
>          Issue Type: New Feature
>          Components: service/cdh
>    Affects Versions: 0.7.1
>            Reporter: Karel Vervaeke
>            Priority: Minor
>
> Currently, the distribution in the cloudera.list file looks like this:
> deb http://archive.cloudera.com/debian lucid-$REPO contrib
> deb-src http://archive.cloudera.com/debian lucid-$REPO contrib
> It would make sense if you would also be able to override the lucid- part.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to