incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BIGTOP-688) improve hue packaging via making virtual env relocatable and moving DB files into /var/lib/hue
Date Thu, 23 Aug 2012 22:42:42 GMT

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

Roman Shaposhnik commented on BIGTOP-688:
-----------------------------------------

@[~anatoli.fomenko]

bq. In install_hue.sh there are 2 variables related to logs: LOG_DIR and DESKTOP_LOG_DIR.
While they may be required by the environment, it may be cleaner to keep it to one.

That's just a convention that we've got going in our _install.sh scripts. I agree that it
is a bit confusing since Hue has the same var, but it is probably best to stay consistent
within the _install.sh scripts.

bq. In hue-app-postinstall.tpl, hue-app.prerm.tpl and other app related files kept some variables
that are removed in other files, such as ROOT=/usr/lib/hue

That's on purpose. We need this functionality to remain for things that are plugins into Hue.
The model of Hue integration in Bigtop is that we prepackage all the core bits together (and
thus do not need to register them dynamically) but things like beeswax and future plugins
still need to run registration code at package install time.

bq. In a few places user name "hue" is used without defining USER=hue

Could you, please, be a bit more specific? I could only see that in chown lines which could
arguably be changed.

bq. Tried a few commands. Met this problem: /usr/lib/hue/build/env/bin]$ sudo ./hue test

In general Bigtop packaging tries to remove test code from packages. Hence any residual code
is not expected to work. An argument could be had that we should do a better job of completely
removing hue test code, but it looks pretty tightly integrated. Do you want to take a look
at it?

bq. Off-topic question: why the build system does not detect change in the src files, only
`rm -rf <component>/build`?

Which build system are you referring to? The Bigtop itself or Hue? Can you, please, be more
specific?
                
> improve hue packaging via making virtual env relocatable and moving DB files into /var/lib/hue
> ----------------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-688
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-688
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.5.0
>
>         Attachments: BIGTOP-688.patch.txt
>
>
> Currently Hue packaging does unfortunate things with permissions and mutability of things
under /usr/lib/hue. We should make sure our virtual env is relocatable and can be used in
a R/O fashion and we should move mutable bits (desktop.db and app.reg) under /var/lib/hue.

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

        

Mime
View raw message