You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2013/05/06 16:40:15 UTC

[jira] [Commented] (BIGTOP-969) a few files belong to more than one package

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

Sean Mackrory commented on BIGTOP-969:
--------------------------------------

I have been looking at this with regards to Sqoop (specifically, the contents of /usr/lib/sqoop and its subdirectories). I'm not sure I have a good solution for this that still allows us to keep the -client package as minimal as possible, but if you have any ideas I'd be happy to spend the time to patch this. I'm surprised about /usr/bin/sqoop, though - I only see it in the sqoop-client package. Where else is it showing up?

Other than just being bad style and the potential for confusion and related bugs, are there any consequences of this? I know that the /usr/lib/sqoop issue causes that directory to remain (empty) after removing the packages, but I see that as a minor annoyance that would be nice to fix if / when we come up with a good way to split those packages better. Just wandering if this is connected to any more serious issues as well.
                
> a few files belong to more than one package
> -------------------------------------------
>
>                 Key: BIGTOP-969
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-969
>             Project: Bigtop
>          Issue Type: Bug
>          Components: RPM
>    Affects Versions: 0.6.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.6.0
>
>
> Here's the list:
> {noformat}
> /usr/bin/sqoop
> /usr/lib/sqoop  
> /usr/lib/sqoop/bin
> /usr/lib/hadoop/bin/fuse_dfs 
> /etc/default/hadoop-fuse
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira