couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From micah <...@git.apache.org>
Subject [GitHub] couchdb pull request: Add first stab at a release build script.
Date Tue, 07 Apr 2015 22:39:43 GMT
Github user micah commented on the pull request:

    https://github.com/apache/couchdb/pull/302#issuecomment-90751051
  
    > @micah on make uninstall what is expected to happen with user-data that was created
by the package? Like databases that might still have important data, are they expected to
be rm’d? I understand logs could go, but I’m hesitant to include databases.
    
    regarding user-data, most linux distros follow the File Hierarchy Standard (FHS) and the
package would handle the creation, and optional removal, of this data. For example, on debian,
it would likely be that the package will create /var/lib/couchdb and the configure script
would be run to set that as the directory for this data, and /var/log/couchdb would be be
where logs go. The packaging system usually asks you about those things on removal, asking
you if you want to remove the databases? are you sure? are you REALLY SURE?! So, I dont think
a make distclean/clean etc. should touch that stuff
    
    Regarding the most recent updates, they have eliminated the problems with files changing,
being removed from unpacked source that were in the tarball, great! Now the only problem is
that after the first build, the following ones fail (even after a make distclean) because
these files remain:
    
    tmp/
    dev/boot_node.beam
    dev/data
    dev/lib
    dev/pbkdf2.pyc
    log/crash.log
    dev/logs
    
    The other issue I've been struggling with is that even if I pass a relative path to the
-p option to configure, its still trying to use the absolute path on installation. So for
example, I've been trying to do ./configure -p debian/couchdb/usr (here because this is where
the package wants the resulting build so it can then take everything in there and make a package
that would then install into /usr), but during the make install phase this happens:
    
    ```
    mkdir: cannot create directory ‘/usr/local/couchdb’: Permission denied
    ```
    It makes sense that I get a permission denied, because I am building as my unprivileged
user, but I dont know why it is trying to use that directory, when I specified the -p option.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message