You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "June Fang (Created) (JIRA)" <ji...@apache.org> on 2011/09/30 11:07:46 UTC

[jira] [Created] (ZOOKEEPER-1211) C client's package name

C client's package name
-----------------------

                 Key: ZOOKEEPER-1211
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1211
             Project: ZooKeeper
          Issue Type: Bug
          Components: c client
    Affects Versions: 3.3.3
         Environment: centos 5
            Reporter: June Fang
            Priority: Trivial


the package name of c client is "c-client-src",
which lead the include file to be installed to /usr/local/include/c-client-src.

it's a bit annoying since user need to manual rename it to zookeeper.

i think there are two fix,
1) change autoconf package name to "zookeeper", then the header will be installed to
   zookeeper subdir, which is consistent with the README;
2) change pkginclude_HEADER to include_HEADER, which will install headers to /usr/local/include.


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

        

[jira] [Commented] (ZOOKEEPER-1211) C client's package name

Posted by "June Fang (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126304#comment-13126304 ] 

June Fang commented on ZOOKEEPER-1211:
--------------------------------------

seems so, this bug could be closed.
but i found another related bug which is also annoying, which i will create another bug.
                
> C client's package name
> -----------------------
>
>                 Key: ZOOKEEPER-1211
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1211
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.3.3
>         Environment: centos 5
>            Reporter: June Fang
>            Priority: Trivial
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> the package name of c client is "c-client-src",
> which lead the include file to be installed to /usr/local/include/c-client-src.
> it's a bit annoying since user need to manual rename it to zookeeper.
> i think there are two fix,
> 1) change autoconf package name to "zookeeper", then the header will be installed to
>    zookeeper subdir, which is consistent with the README;
> 2) change pkginclude_HEADER to include_HEADER, which will install headers to /usr/local/include.

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

        

[jira] [Resolved] (ZOOKEEPER-1211) C client's package name

Posted by "Mahadev konar (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar resolved ZOOKEEPER-1211.
--------------------------------------

    Resolution: Duplicate
    
> C client's package name
> -----------------------
>
>                 Key: ZOOKEEPER-1211
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1211
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.3.3
>         Environment: centos 5
>            Reporter: June Fang
>            Priority: Trivial
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> the package name of c client is "c-client-src",
> which lead the include file to be installed to /usr/local/include/c-client-src.
> it's a bit annoying since user need to manual rename it to zookeeper.
> i think there are two fix,
> 1) change autoconf package name to "zookeeper", then the header will be installed to
>    zookeeper subdir, which is consistent with the README;
> 2) change pkginclude_HEADER to include_HEADER, which will install headers to /usr/local/include.

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

        

[jira] [Commented] (ZOOKEEPER-1211) C client's package name

Posted by "Mahadev konar (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122521#comment-13122521 ] 

Mahadev konar commented on ZOOKEEPER-1211:
------------------------------------------

Duplicate of ZOOKEEPER-1033?
                
> C client's package name
> -----------------------
>
>                 Key: ZOOKEEPER-1211
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1211
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.3.3
>         Environment: centos 5
>            Reporter: June Fang
>            Priority: Trivial
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> the package name of c client is "c-client-src",
> which lead the include file to be installed to /usr/local/include/c-client-src.
> it's a bit annoying since user need to manual rename it to zookeeper.
> i think there are two fix,
> 1) change autoconf package name to "zookeeper", then the header will be installed to
>    zookeeper subdir, which is consistent with the README;
> 2) change pkginclude_HEADER to include_HEADER, which will install headers to /usr/local/include.

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