autoproj 1.4.3 → 1.4.4

data/History.txt

@@ -1,3 +1,6 @@
+= Version 1.4.4
+ * really fix the bug mentioned in 1.4.3
+
 = Version 1.4.3
  * quickfix installations that have no layouts
 

data/doc/guide/config.yaml

@@ -15,8 +15,6 @@
 # The available configuration options can be listed using the `webgen config`
 # command, for example: `webgen config sourcehandler` will list all options starting
 # with sourcehandler.
-default_processing_pipeline:
-    Page: tags,maruku,blocks
 
 default_meta_info:
     Webgen::SourceHandler::Page:
@@ -28,3 +26,4 @@ tag.breadcrumbtrail.omit_index_path: true
 
 tag.coderay.line_numbers: false
 tag.coderay.lang: ruby
+

data/doc/guide/src/customization.page

@@ -11,8 +11,7 @@ The <tt>layout</tt> section of <tt>autoproj/manifest</tt> offers two things:
  * build packages in specific subdirectories
 
 This section lists packages or package sets that ought to be built by autoproj.
-For instance, in the following example, only the <tt>orocos/rtt</tt> and
-<tt>orocos/ocl</tt>
+For instance, in the following example, only the <tt>orocos/rtt</tt> and <tt>orocos/ocl</tt>
 packages of the rubim.orocos source will be built. The other will be excluded
 from the build.
 
@@ -46,7 +45,7 @@ layout:
 Configuration files like <tt>autoproj/manifest</tt> are YAML file. As such, they
 aresensible to indentation. The snippet above should be read as: in the layout, there is first a "lib" part and second the packages whose names start with "orocos/" _(first level of indentation)_. In the "lib" part, the packages are "typelib", "utilmm"
  and "utilrb" _(second level of indentation)_. 
-{.warning}
+{: .warning}
 
 Alternatively, the example above could be written:
 {coderay:: yaml}
@@ -59,7 +58,7 @@ Finally, names of sublayouts can be used as arguments in the autoproj command
 line, instead of package names:
 
 autoproj build lib
-{.commandline}
+{: .commandline}
 
 Removing packages from the build
 --------------------------------
@@ -121,7 +120,7 @@ Building local packages
 
 You can list local packages that are not in an imported package set by placing
 the definitions in autoproj/, in a file ending with <tt>.autobuild</tt>. See [this
-page](source_yml.html) for information on how to write autobuild files.
+page](package_sets/autobuild.html) for information on how to write autobuild files.
 
 Setting up the path to specific commands (make, parallel builds)
 ----------------------------------------------------------------
@@ -178,18 +177,12 @@ layout:
 If the command line is
 
 autoproj build modules/logger
-{.cmdline}
+{: .cmdline}
 
-then only modules/logger and modules/base will be built -- assuming
-modules/logger depends on modules/base -- but typelib will be left alone
-_regardless of its state_. It may speed up the build process tremendously, but
-also may generate errors if other packages needed to be updated.
-
-Idem, if the command line is:
+then modules/logger and its dependencies will be built. Idem, if the command line is:
 
 autoproj build asguard
-{.cmdline}
+{: .cmdline}
 
-then all packages or asguard/ are built _but none of the dependencies that are
-defined in other places in the layout_.
+then all packages or asguard/ are built, including their dependencies
 

data/doc/guide/src/default.css

@@ -293,6 +293,10 @@ margin-left: 2.5em;
 pre {
 margin-left: 2.5em;
 }
+code {
+    font: monospace;
+}
+
 
 /* Original open source design by Andreas Viklund - http://andreasviklund.com
 Released through OSWD.org */

data/doc/guide/src/error_messages.page

@@ -13,5 +13,5 @@ the packages that you requested to build. Two solutions: (i) the package should
 *not* depend on it, and you should modify the [package's
 manifest.xml](package_sets/manifest-xml.html) file. (ii)
 the package should depend on it and you should list the OS package in [the
-relevant osdeps file](osdeps.html)
+relevant osdeps file](package_sets/osdeps.html)
 

data/doc/guide/src/package_sets/autobuild.page

@@ -120,7 +120,7 @@ pkg.depends_on "package_name"
 {coderay}
 
 In the same way, if the source package depends on an OS package (see
-[Prepackaged dependencies](os_deps.html) for details), you can use
+[Prepackaged dependencies](osdeps.html) for details), you can use
 
 {coderay:: ruby}
 pkg.depends_on_os_package "package_name"

data/doc/guide/src/package_sets/osdeps.page

@@ -11,9 +11,9 @@ Defining dependencies between source packages and OS packages
 
 These dependencies can be defined in two ways:
 
- * by adding a <tt>&lt;osdep name="depname" /&gt;</tt> tag in the package's
+ * by adding a `<osdep name="depname" />`  tag in the package's
    [manifest.xml](manifest-xml.html)
- * by calling <tt>pkg.depends_on_os_package("depname")</tt> [in the autobuild
+ * by calling `pkg.depends_on_os_package("depname")` [in the autobuild
    file](autobuild.html).
 
 In both cases, depname is used as a key to find the OS package definition in the
@@ -24,46 +24,46 @@ OS packages
 
 The general format of the an OS package definition:
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 name:
     distribution1,distribution2:
         version1,version2: [package_name1, package_name2]
-{coderay}
+~~~~~~~~~~~~~~~~~~
 
-Where 'name' is the name used to declare the dependency (see above),
-<tt>distribution*</tt> the name of the distribution and <tt>version*</tt> the
-distribution's version, and <tt>package_name*</tt> the name of the package in
+Where 'name' is the name used to declare the dependency (see above), `distribution`
+the name of the distribution and <tt>version</tt> the
+distribution's version, and <tt>package_name</tt> the name of the package in
 the underlying OS.
 
-Since the osdeps file is a YAML file, <tt>[package_name1, package_name2]</tt> can also be written
+Since the osdeps file is a YAML file, it could also be written
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 name:
     distribution1,distribution2:
         version1,version2:
             - package_name1
             - package_name2
-{coderay}
+~~~~~~~~~~~~~~~~~~
 
 If only one package needs to be installed, one can use the shortcut
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 name:
     distribution1,distribution2:
         version1,version2: package_name
-{coderay}
+~~~~~~~~~~~~~~~~~~
 
 Finally, if the package name is version-independent, the version can be omitted:
 
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 name:
     distribution1,distribution2: package_name
-{coderay}
+~~~~~~~~~~~~~~~~~~
 
 Examples:
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 ruby:
     debian,ubuntu:
         9.04,10.04,sid: libruby-dev
@@ -73,7 +73,7 @@ boost:
         - libboost-program1.38-dev
     ubuntu:
         9.04,10.04: libboost-dev
-{coderay}
+~~~~~~~~~~~~~~~~~~
 
 At the time of this writing, autoproj is able to install packages on
 Ubuntu/Debian and Gentoo. Support for other operating systems can be easily
@@ -87,37 +87,37 @@ to by replacing the OS distribution name by 'gem'.
 
 Example:
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 hoe:
     gem:
         hoe
-{coderay}
+~~~~~~~~~~~~~~~~~~
 
 If the OS dep name and the RubyGems name are the same, one can use the shortcut
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 hoe: gem
-{coderay}
+~~~~~~~~~~~~~~~~~~
 
 Note that it is possible to use a mixture of RubyGems and OS packages. For
 instance, the following snippet will both install the gnuplot package and the
 gnuplot RubyGems whenever an osdep on 'gnuplot' is declared.
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 gnuplot:
     gem: gnuplot
     debian: gnuplot
-{coderay}
+~~~~~~~~~~~~~~~~~~
 
 Ignoring some dependencies
 --------------------------
 It is possible that, on some operating systems, a given package should simply be
 ignored. To do so, simply use the 'ignore' keyword. Example:
 
-{coderay:: yaml}
+~~~~~~~~~~~~~~~~~~
 gnuplot:
     gem: gnuplot
     debian: ignore
     ubuntu: gnuplot
-{coderay}
+~~~~~~~~~~~~~~~~~~
 

data/lib/autoproj/manifest.rb

@@ -897,7 +897,7 @@ module Autoproj
                     else
                         # No layout, all packages are selected
                         packages.values.
-                            map { |pkg| package.autobuild.name }
+                            map { |pkg| pkg.autobuild.name }
                     end
             names = names.delete_if { |pkg_name| excluded?(pkg_name) }
             names.to_set

data/lib/autoproj/version.rb

@@ -1,3 +1,3 @@
 module Autoproj
-    VERSION = "1.4.3"
+    VERSION = "1.4.4"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: autoproj
 version: !ruby/object:Gem::Version 
-  version: 1.4.3
+  version: 1.4.4
 platform: ruby
 authors: 
 - Sylvain Joyeux