Difference between pages "Bash by Example, Part 3" and "Help talk:Funtoo Editing Guidelines"

From Funtoo
(Difference between pages)
Jump to navigation Jump to search
m
 
m (more details)
 
Line 1: Line 1:
{{Article
{{DISQUS}}
|Subtitle=Exploring the ebuild system
|Summary=Few people know that the original version of Portage was an evolution of a simple script that I wrote for a bash tutorial. Here's the article that contains the first version of ebuild! Learn how to script by creating a minimal build script.
|Author=Drobbins
|Previous in Series=Bash by Example, Part 2
}}
=== Enter the ebuild system ===
I've really been looking forward to this third and final ''Bash by example'' article, because now that we've already covered bash programming fundamentals in [[Bash by example, Part1|Part 1]] and [[Bash by example, Part 2|Part 2]], we can focus on more advanced topics, like bash application development and program design. For this article, I will give you a good dose of practical, real-world bash development experience by presenting a project that I've spent many hours coding and refining: the Gentoo Linux ebuild system.


As the creator of Gentoo Linux and the guy behind Funtoo Linux, one of my primary responsibilities is to make sure that all of the operating system packages (similar to RPM packages) are created properly and work together. As you probably know, a standard Linux system is not composed of a single unified source tree (like BSD), but is actually made up of about 25+ (As of 2015, over 100! -Ed) core packages that work together. Some of the packages include:
Please keep DISQUS chats at the top of talk pages.


{{TableStart}}
__TOC__
<tr><td class="active">Package</td><td class="active">Description</td></tr>
<tr><td>linux</td><td>The actual kernel</td></tr>
<tr><td>util-linux</td><td>A collection of miscellaneous Linux-related programs</td></tr>
<tr><td>e2fsprogs</td><td>A collection of ext2 filesystem-related utilities</td></tr>
<tr><td>glibc</td><td>The GNU C library</td></tr>
{{TableEnd}}


{{Note|Gentoo fans: the original text above used to say "I'm the chief architect of Gentoo Linux, a next-generation Linux OS currently in beta. One of my primary responsibilities is to make sure that all of the binary packages (similar to RPM packages) are created properly and work together." This is noteworthy due to the fact that the initial focus of Gentoo was to provide working binary packages.}}


Each package is in its own tarball and is maintained by separate independent developers, or teams of developers. To create a distribution, each package has to be separately downloaded, compiled, and packaged. Every time a package must be fixed, upgraded, or improved, the compilation and packaging steps must be repeated (and this gets old really fast). To help eliminate the repetitive steps involved in creating and updating packages, I created the ebuild system, written almost entirely in bash. To enhance your bash knowledge, I'll show you how I implemented the unpack and compile portions of the ebuild system, step by step. As I explain each step, I'll also discuss why certain design decisions were made. By the end of this article, not only will you have an excellent grasp of larger-scale bash programming projects, but you'll also have implemented a good portion of a complete auto-build system.
=== Fancy Boxes ===
TODO: Describe fancy* boxes, and explain the most fool-proof way of using them. Use this format, exactly:


=== Why bash? ===
{{fancyimportant|1=
Bash is an essential component of the Gentoo Linux ebuild system. It was chosen as ebuild's primary language for a number of reasons. First, it has an uncomplicated and familiar syntax that is especially well suited for calling external programs. An auto-build system is "glue code" that automates the calling of external programs, and bash is very well suited to this type of application. Second, Bash's support for functions allowed the ebuild system to have modular, easy-to-understand code. Third, the ebuild system takes advantage of bash's support for environment variables, allowing package maintainers and developers to configure it easily, on-the-fly.
Now you can put lots of funky stuff in here, like <tt>html</tt> tags, etc, and not
have a problem with the parameter getting passed as the first parameter.


=== Build process review ===
Cool!
Before we look at the ebuild system, let's review what's involved in getting a package compiled and installed. For our example, we will look at the "sed" package, a standard GNU text stream editing utility that is part of all Linux distributions. First, download the source tarball ('''sed-3.02.tar.gz''') (see [[#Resources|Resources]]). We will store this archive in '''/usr/src/distfiles''', a directory we will refer to using the environment variable <span style="color:green">$DISTDIR</span>. <span style="color:green">$DISTDIR</span> is the directory where all of our original source tarballs live; it's a big vault of source code.
}}
 
Our next step is to create a temporary directory called '''work''', which houses the uncompressed sources. We'll refer to this directory later using the <span style="color:green">$WORKDIR</span> environment variable. To do this, change to a directory where we have write permission and type the following:
<source lang="bash">
$ mkdir work
$ cd work
$ tar xzf /usr/src/distfiles/sed-3.02.tar.gz
</source>
The tarball is then decompressed, creating a directory called '''sed-3.02''' that contains all of the sources. We'll refer to the '''sed-3.02''' directory later using the environment variable <span style="color:green">$SRCDIR</span>. To compile the program, type the following:
<source lang="bash">
$ cd sed-3.02
$ ./configure --prefix=/usr
(autoconf generates appropriate makefiles, this can take a while)
 
$ make
 
(the package is compiled from sources, also takes a bit of time)
</source>
We're going to skip the "make install" step, since we are just covering the unpack and compile steps in this article. If we wanted to write a bash script to perform all these steps for us, it could look something like this:
<source lang="bash">
#!/usr/bin/env bash
 
if [ -d work ]
then
# remove old work directory if it exists
      rm -rf work
fi
mkdir work
cd work
tar xzf /usr/src/distfiles/sed-3.02.tar.gz
cd sed-3.02
./configure --prefix=/usr
make
</source>
 
=== Generalizing the code ===
Although this autocompile script works, it's not very flexible. Basically, the bash script just contains the listing of all the commands that were typed at the command line. While this solution works, it would be nice to make a generic script that can be configured quickly to unpack and compile any package just by changing a few lines. That way, it's much less work for the package maintainer to add new packages to the distribution. Let's take a first stab at doing this by using lots of different environment variables, making our build script more generic:
<source lang="bash">
#!/usr/bin/env bash
 
# P is the package name
 
P=sed-3.02
 
# A is the archive name
 
A=${P}.tar.gz
 
export ORIGDIR=`pwd`
export WORKDIR=${ORIGDIR}/work
export SRCDIR=${WORKDIR}/${P}
 
if [ -z "$DISTDIR" ]
then
# set DISTDIR to /usr/src/distfiles if not already set
        DISTDIR=/usr/src/distfiles
fi
export DISTDIR
 
if [ -d ${WORKDIR} ]
then   
# remove old work directory if it exists
        rm -rf ${WORKDIR}
fi
 
mkdir ${WORKDIR}
cd ${WORKDIR}
tar xzf ${DISTDIR}/${A}
cd ${SRCDIR}
./configure --prefix=/usr
make
</source>
We've added a lot of environment variables to the code, but it still does basically the same thing. However, now, to compile any standard GNU autoconf-based source tarball, we can simply copy this file to a new file (with an appropriate name to reflect the name of the new package it compiles), and then change the values of <span style"color:green:>$A</span> and <span style"color:green:>$P</span> to new values. All other environment variables automatically adjust to the correct settings, and the script works as expected. While this is handy, there's a further improvement that can be made to the code. This particular code is much longer than the original "transcript" script that we created. Since one of the goals for any programming project should be the reduction of complexity for the user, it would be nice to dramatically shrink the code, or at least organize it better. We can do this by performing a neat trick -- we'll split the code into two separate files. Save this file as '''sed-3.02.ebuild''':
<source lang="bash">
#the sed ebuild file -- very simple!
P=sed-3.02
A=${P}.tar.gz
</source>
Our first file is trivial, and contains only those environment variables that must be configured on a per-package basis. Here's the second file, which contains the brains of the operation. Save this one as "ebuild" and make it executable:
<source lang="bash">
#!/usr/bin/env bash
 
 
if [ $# -ne 1 ]
then
        echo "one argument expected."
        exit 1
fi
 
if [ -e "$1" ]
then
        source $1
else
        echo "ebuild file $1 not found."
        exit 1
fi
 
export ORIGDIR=`pwd`
export WORKDIR=${ORIGDIR}/work
export SRCDIR=${WORKDIR}/${P}
 
if [ -z "$DISTDIR" ]
then
        # set DISTDIR to /usr/src/distfiles if not already set
        DISTDIR=/usr/src/distfiles
fi
export DISTDIR
 
if [ -d ${WORKDIR} ]
then   
        # remove old work directory if it exists
        rm -rf ${WORKDIR}
fi
 
mkdir ${WORKDIR}
cd ${WORKDIR}
tar xzf ${DISTDIR}/${A}
cd ${SRCDIR}
./configure --prefix=/usr
make
</source>
Now that we've split our build system into two files, I bet you're wondering how it works. Basically, to compile sed, type:
<source lang="bash">
$ ./ebuild sed-3.02.ebuild
</source>
When "ebuild" executes, it first tries to "source" variable <span style="color:green">$1</span>. What does this mean? From my previous article, recall that <span style="color:green">$1</span> is the first command line argument -- in this case, '''sed-3.02.ebuild'''. In bash, the "source" command reads in bash statements from a file, and executes them as if they appeared immediately in the file the "source" command is in. So, "source ${1}" causes the "ebuild" script to execute the commands in '''sed-3.02.ebuild''', which cause <span style="color:green">$P</span> and <span style="color:green">$A</span> to be defined. This design change is really handy, because if we want to compile another program instead of sed, we can simply create a new '''.ebuild''' file and pass it as an argument to our "ebuild" script. That way, the '''.ebuild''' files end up being really simple, while the complicated brains of the ebuild system get stored in one place -- our "ebuild" script. This way, we can upgrade or enhance the ebuild system simply by editing the "ebuild" script, keeping the implementation details outside of the ebuild files. Here's a sample ebuild file for <span style="color:green">gzip</span>:
<source lang="bash">
#another really simple ebuild script!
P=gzip-1.2.4a
A=${P}.tar.gz
</source>
 
=== Adding functionality ===
OK, we're making some progress. But, there is some additional functionality I'd like to add. I'd like the ebuild script to accept a second command-line argument, which will be <span style="color:green">compile</span>, <span style="color:green">unpack</span>, or <span style="color:green">all</span>. This second command-line argument tells the ebuild script which particular step of the build process to perform. That way, I can tell ebuild to unpack the archive, but not compile it (just in case I need to inspect the source archive before compilation begins). To do this, I'll add a case statement that will test variable <span style="color:green">$2</span>, and do different things based on its value. Here's what the code looks like now:
<source lang="bash">
#!/usr/bin/env bash
 
if [ $# -ne 2 ]
then
        echo "Please specify two args - .ebuild file and unpack, compile or all"
        exit 1
fi
 
 
if [ -z "$DISTDIR" ]
then
# set DISTDIR to /usr/src/distfiles if not already set
        DISTDIR=/usr/src/distfiles
fi
export DISTDIR
 
ebuild_unpack() {
        #make sure we're in the right directory
        cd ${ORIGDIR}
       
        if [ -d ${WORKDIR} ]
        then   
                rm -rf ${WORKDIR}
        fi
 
        mkdir ${WORKDIR}
        cd ${WORKDIR}
        if [ ! -e ${DISTDIR}/${A} ]
        then
            echo "${DISTDIR}/${A} does not exist.  Please download first."
            exit 1
        fi   
        tar xzf ${DISTDIR}/${A}
        echo "Unpacked ${DISTDIR}/${A}."
        #source is now correctly unpacked
}
 
 
ebuild_compile() {
       
        #make sure we're in the right directory
        cd ${SRCDIR}
        if [ ! -d "${SRCDIR}" ]
        then
                echo "${SRCDIR} does not exist -- please unpack first."
                exit 1
        fi
        ./configure --prefix=/usr
        make   
}
 
export ORIGDIR=`pwd`
export WORKDIR=${ORIGDIR}/work
 
if [ -e "$1" ]
then
        source $1
else
        echo "Ebuild file $1 not found."
        exit 1
fi
 
export SRCDIR=${WORKDIR}/${P}
 
case "${2}" in
        unpack)
                ebuild_unpack
                ;;
        compile)
                ebuild_compile
                ;;
        all)
                ebuild_unpack
                ebuild_compile
                ;;
        *)
                echo "Please specify unpack, compile or all as the second arg"
                exit 1
                ;;
esac
</source>
We've made a lot of changes, so let's review them. First, we placed the compile and unpack steps in their own functions, and called <span style="color:green:>ebuild_compile()</span> and <span style="color:green">ebuild_unpack()</span>, respectively. This is a good move, since the code is getting more complicated, and the new functions provide some modularity, which helps to keep things organized. On the first line in each function, I explicitly <span style="color:green">cd</span> into the directory I want to be in because, as our code is becoming more modular rather than linear, it's more likely that we might slip up and execute a function in the wrong current working directory. The <span style="color:green">cd</span> commands explicitly put us in the right place, and prevent us from making a mistake later -- an important step -- especially if you will be deleting files inside the functions.
 
Also, I added a useful check to the beginning of the <span style="color:green">ebuild_compile()</span> function. Now, it checks to make sure the <span style="color:green">$SRCDIR</span> exists, and, if not, it prints an error message telling the user to unpack the archive first, and then exits. If you like, you can change this behavior so that if <span style="color:green">$SRCDIR</span> doesn't exist, our ebuild script will unpack the source archive automatically. You can do this by replacing <span style="color:green">ebuild_compile()</span> with the following code:
<source lang="bash">
ebuild_compile() {
        #make sure we're in the right directory
        if [ ! -d "${SRCDIR}" ]
        then
                ebuild_unpack
        fi
        cd ${SRCDIR}
        ./configure --prefix=/usr
        make   
}
</source>
One of the most obvious changes in our second version of the ebuild script is the new case statement at the end of the code. This case statement simply checks the second command-line argument, and performs the correct action, depending on its value. If we now type:
<source lang="bash">
$ ebuild sed-3.02.ebuild
</source>
We'll actually get an error message. ebuild now wants to be told what to do, as follows:
<source lang="bash">
$ ebuild sed-3.02.ebuild unpack
</source>
or:
<source lang="bash">
$ ebuild sed-3.02.ebuild compile
</source>
or:
<source lang="bash">
$ ebuild sed-3.02.ebuild all
</source>
 
{{fancyimportant|If you provide a second command-line argument, other than those listed above, you get an error message (the * clause), and the program exits.}}
 
=== Modularizing the code ===
Now that the code is quite advanced and functional, you may be tempted to create several more ebuild scripts to unpack and compile your favorite programs. If you do, sooner or later you'll come across some sources that do not use autoconf (<span style="color:green">./configure</span>) or possibly others that have non-standard compilation processes. We need to make some more changes to the ebuild system to accommodate these programs. But before we do, it is a good idea to think a bit about how to accomplish this.
 
One of the great things about hard-coding <span style="color:green">./configure --prefix=/usr; make</span> into our compile stage is that, most of the time, it works. But, we must also have the ebuild system accommodate sources that do not use autoconf or normal Makefiles. To solve this problem, I propose that our ebuild script should, by default, do the following:
 
# If there is a configure script in <span style="color:green">${SRCDIR}</span>, execute it as follows: <span style="color:green">./configure --prefix=/usr</span>. Otherwise, skip this step.
# Execute the following command: make
 
Since ebuild only runs configure if it actually exists, we can now automatically accommodate those programs that don't use autoconf and have standard makefiles. But what if a simple "make" doesn't do the trick for some sources? We need a way to override our reasonable defaults with some specific code to handle these situations. To do this, we'll transform our <span style="color:green">ebuild_compile()</span> function into two functions. The first function, which can be looked at as a "parent" function, will still be called <span style="color:green">ebuild_compile()</span>. However, we'll have a new function, called <span style="color:green">user_compile()</span>, which contains only our reasonable default actions:
<source lang="bash">
user_compile() {
        #we're already in ${SRCDIR}
        if [ -e configure ]
        then
                #run configure script if it exists
                ./configure --prefix=/usr
        fi
        #run make
        make
}             
 
ebuild_compile() {
        if [ ! -d "${SRCDIR}" ]
        then
                echo "${SRCDIR} does not exist -- please unpack first."
                exit 1
        fi
        #make sure we're in the right directory
        cd ${SRCDIR}
        user_compile
}
</source>
It may not seem obvious why I'm doing this right now, but bear with me. While the code works almost identically to our previous version of ebuild, we can now do something that we couldn't do before -- we can override <span style="color:green">user_compile()</span> in '''sed-3.02.ebuild'''. So, if the default <span style="color:green:>user_compile()</span> function doesn't meet our needs, we can define a new one in our '''.ebuild''' file that contains the commands required to compile the package. For example, here's an ebuild file for <span style="color:green">e2fsprogs-1.18</span>, which requires a slightly different <span style="color:green">./configure</span> line:
<source lang="bash">
#this ebuild file overrides the default user_compile()
P=e2fsprogs-1.18
A=${P}.tar.gz
user_compile() {
      ./configure --enable-elf-shlibs
      make
}
</source>
Now, <span style="color:green">e2fsprogs</span> will be compiled exactly the way we want it to be. But, for most packages, we can omit any custom <span style="color:green">user_compile()</span> function in the '''.ebuild''' file, and the default user_compile() function is used instead.
 
How exactly does the ebuild script know which user_compile() function to use? This is actually quite simple. In the ebuild script, the default <span style="color:green">user_compile()</span> function is defined before the '''e2fsprogs-1.18.ebuild''' file is sourced. If there is a <span style="color:green">user_compile()</span> in '''e2fsprogs-1.18.ebuild''', it overwrites the default version defined previously. If not, the default <span style="color:green">user_compile()</span> function is used.
 
This is great stuff; we've added a lot of flexibility without requiring any complex code if it's not needed. We won't cover it here, but you could also make similar modifications to <span style="color:green">ebuild_unpack()</span> so that users can override the default unpacking process. This could come in handy if any patching has to be done, or if the files are contained in multiple archives. It is also a good idea to modify our unpacking code so that it recognizes bzip2-compressed tarballs by default.


=== Configuration files ===
=== watching pages ===
We've covered a lot of sneaky bash techniques so far, and now it's time to cover one more. Often, it's handy for a program to have a global configuration file that resides in '''/etc'''. Fortunately, this is easy to do using bash. Simply create the following file and save it as '''/etc/ebuild.conf''':
we should have a section dedicated to explaining how to watch pages that an editor is knowledgeable about, and how to use the watch list to keep the pages clean, concise, and accurate.
<source lang="bash">
ie if i know about the web server stack i watch that, and pages related to that...  (i think i might need to turn off watching pages i touch automatically...)
# /etc/ebuild.conf: set system-wide ebuild options in this file


# MAKEOPTS are options passed to make
To watch, or unwatch a page:
MAKEOPTS="-j2"
in the menu bar {{c|Actions > Watch}} or {{c|Actions > Unwatch}}
</source>
In this example, I've included just one configuration option, but you could include many more. One of the beautiful things about bash is that this file can be parsed by simply sourcing it. This is a design trick that works with most interpreted languages. After '''/etc/ebuild.conf''' is sourced, <span style="color:green">$MAKEOPTS</span> is defined inside our ebuild script. We'll use it to allow the user to pass options to make. Normally, this option would be used to allow the user to tell ebuild to do a parallel make. This is explained below.


{{fancynote|'''What is a parallel make?''' <nowiki>To speed compilation on multiprocessor systems, make supports compiling a program in parallel. This means that instead of compiling just one source file at a time, make compiles a user-specified number of source files simultaneously (so those extra processors in a multiprocessor system are used). Parallel makes are enabled by passing the -j # option to make, as follows: make -j4 MAKE="make -j4". This code instructs make to compile four programs simultaneously. The MAKE="make -j4" argument tells make to pass the -j4 option to any child make processes it launches.</nowiki>}}
To display the watchlist:
in the menu bar {{c|account > watchlist}}


Here's the final version of our ebuild program:
rss codes should be also generated to easily track the watch list so everyone gets pinged when a change occurs.  [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) 03:55, March 27, 2015 (UTC)
<source lang="bash">
#!/usr/bin/env bash


if [ $# -ne 2 ]
=== Special Characters ===
then
        echo "Please specify ebuild file and unpack, compile or all"
        exit 1
fi


source /etc/ebuild.conf
To produce pipes: <pre>{{!}}</pre>
generates: {{!}}


if [ -z "$DISTDIR" ]
To produce equals: <pre>{{=}}</pre>
then
generates: {{=}}
        # set DISTDIR to /usr/src/distfiles if not already set
        DISTDIR=/usr/src/distfiles
fi
export DISTDIR


ebuild_unpack() {
=== delete template ===
        #make sure we're in the right directory
to flag a page as a candidate for deletion, insert
        cd ${ORIGDIR}
<pre>{{delete}}</pre>
       
at the top of a page.
        if [ -d ${WORKDIR} ]
        then   
                rm -rf ${WORKDIR}
        fi


        mkdir ${WORKDIR}
{{delete}}
        cd ${WORKDIR}
[[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) 16:54, 20 September 2014 (UTC)
        if [ ! -e ${DISTDIR}/${A} ]
        then
                echo "${DISTDIR}/${A} does not exist.  Please download first."
                exit 1
        fi
        tar xzf ${DISTDIR}/${A}
        echo "Unpacked ${DISTDIR}/${A}."
        #source is now correctly unpacked
}


user_compile() {
=== Minor edits ===
        #we're already in ${SRCDIR}
Check minor edits to note that your commit is a small commit.  A minor edit can be filtered out of logs when searching through them.
        if [ -e configure ]
        then
                #run configure script if it exists
                ./configure --prefix=/usr
        fi
        #run make
        make $MAKEOPTS MAKE="make $MAKEOPTS"  
}


ebuild_compile() {
=== video playlists ===
        if [ ! -d "${SRCDIR}" ]
i have several examples of how to embed playlists in [[Programming]] but there are no examples in how to wiki.  
        then
                echo "${SRCDIR} does not exist -- please unpack first."
                exit 1
        fi
        #make sure we're in the right directory
        cd ${SRCDIR}
        user_compile
}


export ORIGDIR=`pwd`
=== links ===
export WORKDIR=${ORIGDIR}/work
fixing a broken link brought this subject to my attention.
[www.link.com is this a bug?] && [link.com shouldn't this work?] do not work...  brackets or not.


if [ -e "$1" ]
no protocol defined external links <nowiki>[//test.com //test.com]</nowiki> produces (use these style links)
then
[//test.com //test.com]
        source $1
else
        echo "Ebuild file $1 not found."
        exit 1
fi


export SRCDIR=${WORKDIR}/${P}
no bracket links:
http://google.com
(regardless that this service only offers https)


case "${2}" in
=== Image Embedding ===
        unpack)
To embed images:
                ebuild_unpack
<pre>[[File:Nginx.gif|class=img-responsive|center]]</pre>
                ;;
[[File:Nginx.gif|class=img-responsive|center]]
        compile)
                ebuild_compile
                ;;
        all)
                ebuild_unpack
                ebuild_compile
                ;;
        *)
                echo "Please specify unpack, compile or all as the second arg"
                exit 1
                ;;
esac
</source>
Notice '''/etc/ebuild.conf''' is sourced near the beginning of the file. Also, notice that we use <span style="color:green">$MAKEOPTS</span> in our default <span style="color:green">user_compile()</span> function. You may be wondering how this will work -- after all, we refer to <span style="color:green">$MAKEOPTS</span> before we source '''/etc/ebuild.conf''', which actually defines <span style="color:green">$MAKEOPTS</span> in the first place. Fortunately for us, this is OK because variable expansion only happens when <span style="color:green">user_compile()</span> is executed. By the time <span style="color:green">user_compile()</span> is executed, '''/etc/ebuild.conf''' has already been sourced, and <span style="color:green">$MAKEOPTS</span> is set to the correct value.


=== Wrapping it up ===
=== how to talk pages ===
We've covered a lot of bash programming techniques in this article, but we've only touched the surface of the power of bash. For example, the production Gentoo Linux ebuild system not only automatically unpacks and compiles each package, but it can also:


* Automatically download the sources if they are not found in $DISTDIR
we need a section explaining how to indent for step2 of talk threads
* Verify that the sources are not corrupted by using MD5 message digests
:ie conversation 2
* If requested, install the compiled application into the live filesystem, recording all installed files so that the package can be easily uninstalled at a later date.
:: ie convo 3
* If requested, package the compiled application in a tarball (compressed the way you like it) so that it can be installed later, on another computer, or during the CD-based installation process (if you are building a distribution CD)
::: we need info on using tilde's to sign and date etc... noting that its good practice to sign with 4 ~
{{tip| <pre>~~~ && ~~~~ && ~~~~~</pre> produces [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) && [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) 22:41, 26 September 2014 (UTC) && 22:41, 26 September 2014 (UTC)}}


In addition, the production ebuild system has several other global configuration options, allowing the user to specify options such as what optimization flags to use during compilation, and whether optional support for packages like GNOME and slang should be enabled by default in those packages that support it.
we need a note about user talk pages being a messaging system....  (i put a disqus on my talk page so i get email notifications when people say things to me) [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) 22:41, 26 September 2014 (UTC)


It's clear that bash can accomplish much more than what I've touched on in this series of articles. I hope you've learned a lot about this incredible tool, and are excited about using bash to speed up and enhance your development projects.
=== template requests ===
==== external resources ====
I would like a sexy little widget for by the top of the page with links to: tldp, wikipedia, ohloh, cvedetails, github, sourceforge, etc with sexy little icons.  It will make our pages feel more interwoven with the larger linux community. ;-) [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) 23:30, 2 October 2014 (UTC)


== Resources ==
http://www.cvedetails.com/vendor/12010/Mariadb.html


* Download the source tarball ('''sed-3.02.tar.gz''') from ftp://ftp.gnu.org/pub/gnu/sed.
==== fortune of the day ====
* Read [[Bash by Example, Part 1]].
I'd like a daily fortune rotation on my user page to show im looney tunes ;-) [[User:Threesixes|Threesixes]] ([[User talk:Threesixes|talk]]) 23:30, 2 October 2014 (UTC)
* Read [[Bash by Example, Part 2]].
* Check out the [http://www.gnu.org/software/bash/manual/bash.html bash online reference manual].


__NOTOC__
=== widget requests ===
[[Category:Linux Core Concepts]]
# http://www.mediawikiwidgets.org/Widget:Ohloh_Project for dynamic language summary on packages
[[Category:Articles]]
# http://www.mediawikiwidgets.org/Alexa <-this ones pretty rad
{{ArticleFooter}}
# http://www.mediawikiwidgets.org/AddThis
# adsense, the sites set for traffic, corporate sponsorship is a good idea.  https://www.mediawiki.org/wiki/Extension:Google_AdSense_2

Revision as of 04:16, March 27, 2015


Please keep DISQUS chats at the top of talk pages.



Fancy Boxes

TODO: Describe fancy* boxes, and explain the most fool-proof way of using them. Use this format, exactly:

   Important

Now you can put lots of funky stuff in here, like html tags, etc, and not have a problem with the parameter getting passed as the first parameter.

Cool!

watching pages

we should have a section dedicated to explaining how to watch pages that an editor is knowledgeable about, and how to use the watch list to keep the pages clean, concise, and accurate. ie if i know about the web server stack i watch that, and pages related to that... (i think i might need to turn off watching pages i touch automatically...)

To watch, or unwatch a page: in the menu bar Actions > Watch or Actions > Unwatch

To display the watchlist: in the menu bar account > watchlist

rss codes should be also generated to easily track the watch list so everyone gets pinged when a change occurs. Threesixes (talk) 03:55, March 27, 2015 (UTC)

Special Characters

To produce pipes: 

{{!}}

generates: |

To produce equals: 

{{=}}

generates: =

delete template

to flag a page as a candidate for deletion, insert 

{{delete}}

at the top of a page.

   Warning

This page has been proposed for deletion because it does not meet the Editing Guidelines.
If you disagree, please discuss it here.

Threesixes (talk) 16:54, 20 September 2014 (UTC)

Minor edits

Check minor edits to note that your commit is a small commit. A minor edit can be filtered out of logs when searching through them.

video playlists

i have several examples of how to embed playlists in Programming but there are no examples in how to wiki.

links

fixing a broken link brought this subject to my attention. [www.link.com is this a bug?] && [link.com shouldn't this work?] do not work... brackets or not.

no protocol defined external links [//test.com //test.com] produces (use these style links) //test.com

no bracket links: http://google.com (regardless that this service only offers https)

Image Embedding

To embed images: 

[[File:Nginx.gif|class=img-responsive|center]]
Nginx.gif

how to talk pages

we need a section explaining how to indent for step2 of talk threads

ie conversation 2
ie convo 3
we need info on using tilde's to sign and date etc... noting that its good practice to sign with 4 ~
   Tip
~~~ && ~~~~ && ~~~~~
produces Threesixes (talk) && Threesixes (talk) 22:41, 26 September 2014 (UTC) && 22:41, 26 September 2014 (UTC)

we need a note about user talk pages being a messaging system.... (i put a disqus on my talk page so i get email notifications when people say things to me) Threesixes (talk) 22:41, 26 September 2014 (UTC)

template requests

external resources

I would like a sexy little widget for by the top of the page with links to: tldp, wikipedia, ohloh, cvedetails, github, sourceforge, etc with sexy little icons. It will make our pages feel more interwoven with the larger linux community. ;-) Threesixes (talk) 23:30, 2 October 2014 (UTC)

http://www.cvedetails.com/vendor/12010/Mariadb.html

fortune of the day

I'd like a daily fortune rotation on my user page to show im looney tunes ;-) Threesixes (talk) 23:30, 2 October 2014 (UTC)

widget requests

  1. http://www.mediawikiwidgets.org/Widget:Ohloh_Project for dynamic language summary on packages
  2. http://www.mediawikiwidgets.org/Alexa <-this ones pretty rad
  3. http://www.mediawikiwidgets.org/AddThis
  4. adsense, the sites set for traffic, corporate sponsorship is a good idea. https://www.mediawiki.org/wiki/Extension:Google_AdSense_2
Retrieved from "https://www.funtoo.org/index.php?title=Bash_by_Example,_Part_3&oldid=9426"