couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-373) ./utils/run complains about non-existant directories
Date Sat, 09 Oct 2010 01:19:07 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Joseph Davis updated COUCHDB-373:
--------------------------------------

    Skill Level: New Contributors Level (Easy)

> ./utils/run complains about non-existant directories
> ----------------------------------------------------
>
>                 Key: COUCHDB-373
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-373
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.10
>         Environment: trunk
>            Reporter: Paul Joseph Davis
>            Assignee: Noah Slater
>            Priority: Minor
>
> Executing ./utils/run complains about missing directories
> Steps to reproduce:
> 1. Find a computer that you can install linux on.
> 2. Fetch a copy of an operating system that you can use. I recommed the GNU/Linux Ubuntu
distribution. You can download a copy of it at [1]. If you're new to the GNU/Linux operating
system, I recommend downloading the "Desktop" distribution. At the time of this writing, Ubuntu
9.04 is the most recent release an is the recommended version when following these steps to
reproduce the issue.
> 3. Once your download has completed you should have a local file that has an extension
of ".iso". (An extension is the last three characters of the filename.) "ISO" files is an
archive copy that is commonly used to distributed software that is designed to run from optical
media. See [2] for a more thorough explanation of the format.
> 4. Transfer the ISO file to an optical media that your target system is capable of reading.
(Alternatively you could create a bootable thumb drive [3], but that is outside the scope
of this document.) When transferring the "ISO" file you must be sure to use software that
understands the format. See [4] for further help.
> 5. Place the installation media into your computer and reboot.
> 6. When the BIOS screen [5] appears, press the appropriate key combination to view your
preferred boot device [6]. You'll need to ensure that the drive containing your installation
media is the primary boot device. Exact instructions will vary based on manufacturer and model
of motherboard. Consult Google [7] for more information.
> 7. Installing GNU/Linux will depend on the distribution that you chose. If you followed
these steps to reproduce, the Ubuntu installation procedure provides helpful Graphical User
Interface [8] to assist with the installation procedure. More detail instructions for installation
can be found at [9].
> 8. Assuming that your installation was successful it is always helpful to get acquainted
with the new system. See [10] for a helpful community of Ubuntu users. To proceed with the
rest of these steps you'll need to become familiar with the Command Line Interface [11]. In
the Ubuntu GNU/Linux operating system, this application is called "Terminal" [12]. At the
minimum you will need to be familiar with how to execute commands and perform actions as the
"Superuser" or "Root user" [13]. See [14] for instructions on using the "sudo" (Super User
Do) command line application.
> 9. Install dependencies that CouchDB requires for configuration and compiling. The fastest
method for installing dependencies is to issue the following command in the Terminal application:
>     $ sudo build-dep couchdb
> A note on commands: The above syntax is a method for describing commands in the Terminal
application. The '$' character represents the "prompt" [11]. Commands are entered as a string
of characters and executed by pressing the "Return" key on your keyboard. Sometimes the "Return"
key is referred to by other names, (for instance, on keyboards for languages other than English),
suffice it to say that it is generally the largest key on the right hand side of your keyboard
(disregarding the (possibly non-existant) numeric keypad, and (possibly non-existant) directional
keys.).
> Assuming that command completes successfully, we should be ready to start configuring
and installing CouchDB. If something goes awry, you should be aware that the CouchDB community
is willing to help [15].
> 10. Fetch the Subversion [16] utility. Subversion is a "Revision Control System" [17],
a tool commonly used by programmers to track changes they make to a program. On the Ubuntu
GNU/Linux you can fetch this tool with the following command:
>     $ sudo apt-get install subversion
>     
> If that command fails, I will refer the user once again to the CouchDB community found
at [15].
> 11. Fetch a copy of the CouchDB source code.
>     $ svn co http://svn.apache.org/repos/asf/couchdb/trunk couchdb
> 12. Change into the CouchDB directory
>     $ cd couchdb
> 13. Bootstrap the software. Bootstrapping [18] refers to the process of preparing a source
code distribution (such as the one you have just retrieved) for the configuration process.
A more thorough description of the process can be found at [19].
>     $ ./bootstrap
>     
> 14. Configure the software. Note, although we will not be installing the software in
this guide, the configuration step is where the paths for installation are decided. If you
are building CouchDB for system wide use, you may wish to peruse the Filesystem Hierarchy
Standard (FHS) [20] to get an idea of where you may want to install different portions of
the final build product. Also consult with the CouchDB README that has helpful pointers.
>     $ ./configure
>     
> 15. Now that the software is configured, we are ready to compile it into a running program.
>     $ make
>     
> 16. The following steps involve creating and running CouchDB in a development environment
as this is the configuration affected by this bug. If you desired to install the compiled
program on your system the appropriate command would be:
>     # THIS IS NOT REQUIRED
>     $ sudo make install
>     
> I have placed an obvious note to...
> Damn. My upgrade yesterday broke stuff. I have things to attend to.
> [1] http://www.ubuntu.com/getubuntu/download
> [2] http://en.wikipedia.org/wiki/ISO_image
> [3] http://www.google.com/search?q=bootable+thumb+drive
> [4] http://www.google.com/search?q=Burning+an+ISO
> [5] http://en.wikipedia.org/wiki/BIOS
> [6] http://en.wikipedia.org/wiki/Booting#Boot_devices_.28IBM_PC.29
> [7] http://www.google.com
> [8] http://en.wikipedia.org/wiki/Graphical_user_interface
> [9] https://help.ubuntu.com/9.04/installation-guide/i386/index.html
> [10] http://www.ubuntu.com/community
> [11] http://en.wikipedia.org/wiki/Command_line_interface
> [12] https://help.ubuntu.com/community/UsingTheTerminal
> [13] http://en.wikipedia.org/wiki/Root_user
> [14] https://help.ubuntu.com/community/RootSudo
> [15] http://couchdb.apache.org/community/index.html
> [16] http://subversion.tigris.org/
> [17] http://en.wikipedia.org/wiki/Revision_control
> [18] http://en.wikipedia.org/wiki/Bootstrapping_(computing)#Software_bootstrapping
> [19] http://sources.redhat.com/autobook/autobook/autobook_43.html#SEC43

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message