<feed xmlns='http://www.w3.org/2005/Atom'>
<title>project.git/reproduce/config, branch maneage</title>
<subtitle>Core Maneage branch (where all projects derive from)</subtitle>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/'/>
<entry>
<title>New architecture to separate software-building and analysis steps</title>
<updated>2019-04-15T01:24:09+00:00</updated>
<author>
<name>Mohammad Akhlaghi</name>
<email>mohammad@akhlaghi.org</email>
</author>
<published>2019-04-15T00:47:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=313b936b502d22b6a2ff43f560dee0bb51fd01d0'/>
<id>313b936b502d22b6a2ff43f560dee0bb51fd01d0</id>
<content type='text'>
Until now, the software building and analysis steps of the pipeline were
intertwined. However, these steps (of how to build a software, and how to
use it) are logically completely independent.

Therefore with this commit, the pipeline now has a new architecture
(particularly in the `reproduce' directory) to emphasize this distinction:
The `reproduce' directory now has the two `software' and `analysis'
subdirectories and the respective parts of the previous architecture have
been broken up between these two based on their function. There is also no
more `src' directory. The `config' directory for software and analysis is
now mixed with the language-specific directories.

Also, some of the software versions were also updated after some checks
with their webpages.

This new architecture will allow much more focused work on each part of the
pipeline (to install the software and to run them for an analysis).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Until now, the software building and analysis steps of the pipeline were
intertwined. However, these steps (of how to build a software, and how to
use it) are logically completely independent.

Therefore with this commit, the pipeline now has a new architecture
(particularly in the `reproduce' directory) to emphasize this distinction:
The `reproduce' directory now has the two `software' and `analysis'
subdirectories and the respective parts of the previous architecture have
been broken up between these two based on their function. There is also no
more `src' directory. The `config' directory for software and analysis is
now mixed with the language-specific directories.

Also, some of the software versions were also updated after some checks
with their webpages.

This new architecture will allow much more focused work on each part of the
pipeline (to install the software and to run them for an analysis).
</pre>
</div>
</content>
</entry>
<entry>
<title>Replaced all occurances of pipeline in text</title>
<updated>2019-04-14T16:49:55+00:00</updated>
<author>
<name>Mohammad Akhlaghi</name>
<email>mohammad@akhlaghi.org</email>
</author>
<published>2019-04-14T16:48:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=4722ea598edd6b630227404c48c1c09ac527e9b8'/>
<id>4722ea598edd6b630227404c48c1c09ac527e9b8</id>
<content type='text'>
All occurances of "pipeline" have been chanaged to "project" or "template"
withint the text (comments, READMEs, and comments) of the template. The
main template branch is now also named `template'.

This was all because `pipeline' is too generic and couldn't be
distinguished from the base, and customized project.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
All occurances of "pipeline" have been chanaged to "project" or "template"
withint the text (comments, READMEs, and comments) of the template. The
main template branch is now also named `template'.

This was all because `pipeline' is too generic and couldn't be
distinguished from the base, and customized project.
</pre>
</div>
</content>
</entry>
<entry>
<title>Corrected copyright notices and info about adding copyright info</title>
<updated>2019-04-13T22:43:07+00:00</updated>
<author>
<name>Mohammad Akhlaghi</name>
<email>mohammad@akhlaghi.org</email>
</author>
<published>2019-04-13T22:43:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=0cbd2243458611caa2a3564b577987531bcd6934'/>
<id>0cbd2243458611caa2a3564b577987531bcd6934</id>
<content type='text'>
Until now, the files where the people were meant to change didn't have a
proper copyright notice (for example `Copyright (C) YOUR NAME.'). This was
wrong because the license does not convey copyright ownership. So the name
of the file's original author must always be included and when people
modify it (and add their own copyright-able modifications).

With this commit, the file's original author (and email) are added to the
copyright notice and when more than one person modified a file, both names
have their individual copyright notice.

Based on this, the description for adding a copyright notice in
`README-hacking.md' has also been modified.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Until now, the files where the people were meant to change didn't have a
proper copyright notice (for example `Copyright (C) YOUR NAME.'). This was
wrong because the license does not convey copyright ownership. So the name
of the file's original author must always be included and when people
modify it (and add their own copyright-able modifications).

With this commit, the file's original author (and email) are added to the
copyright notice and when more than one person modified a file, both names
have their individual copyright notice.

Based on this, the description for adding a copyright notice in
`README-hacking.md' has also been modified.
</pre>
</div>
</content>
</entry>
<entry>
<title>File is built as a dependency of GCC</title>
<updated>2019-04-12T13:57:12+00:00</updated>
<author>
<name>Raul Infante-Sainz</name>
<email>infantesainz@gmail.com</email>
</author>
<published>2019-04-12T13:57:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=1442a5ebe5f9ca66f25c0f0a585c6ac4083101d8'/>
<id>1442a5ebe5f9ca66f25c0f0a585c6ac4083101d8</id>
<content type='text'>
Until now, we did not have `file'.  It was in other project, where a
problem with `Astrometry-net' software, ends up with the necessity of
having `file' into the pipeline.

With this commit, we add `file' to the project. Since it is a low level
program, it is set in `dependencies-basic.mk' as a prerequisite of GCC.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Until now, we did not have `file'.  It was in other project, where a
problem with `Astrometry-net' software, ends up with the necessity of
having `file' into the pipeline.

With this commit, we add `file' to the project. Since it is a low level
program, it is set in `dependencies-basic.mk' as a prerequisite of GCC.
</pre>
</div>
</content>
</entry>
<entry>
<title>GNU M4 now built as a dependency of GNU Libtool</title>
<updated>2019-04-07T15:39:08+00:00</updated>
<author>
<name>Mohammad Akhlaghi</name>
<email>mohammad@akhlaghi.org</email>
</author>
<published>2019-04-07T15:18:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=a44c029775f512d8b92cabed7585b74d002435be'/>
<id>a44c029775f512d8b92cabed7585b74d002435be</id>
<content type='text'>
On some systems, M4 isn't available, so the linking to the host system
fails, as a result, we can't build GNU Libtool.

The main reason we weren't building M4 was a bug with the most recent GNU C
library
(http://lists.gnu.org/archive/html/bug-gnulib/2019-04/msg00004.html). But I
found a patch used by Arch Linux which fixes the issue and allows M4 to be
built. As a result, the pipeline is now building M4 also and the patched M4
tarball is now uploaded to my own webpage as backup.

While doing the steps above, I also noticed that we weren't using a tab at
the start of the link definitions of `dependencies-basic.mk'. Although its
not necessary, to be consistent, its good for the lines to always start
with a tab.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
On some systems, M4 isn't available, so the linking to the host system
fails, as a result, we can't build GNU Libtool.

The main reason we weren't building M4 was a bug with the most recent GNU C
library
(http://lists.gnu.org/archive/html/bug-gnulib/2019-04/msg00004.html). But I
found a patch used by Arch Linux which fixes the issue and allows M4 to be
built. As a result, the pipeline is now building M4 also and the patched M4
tarball is now uploaded to my own webpage as backup.

While doing the steps above, I also noticed that we weren't using a tab at
the start of the link definitions of `dependencies-basic.mk'. Although its
not necessary, to be consistent, its good for the lines to always start
with a tab.
</pre>
</div>
</content>
</entry>
<entry>
<title>Copyright notice added to all files missing one</title>
<updated>2019-04-06T23:09:14+00:00</updated>
<author>
<name>Mohammad Akhlaghi</name>
<email>mohammad@akhlaghi.org</email>
</author>
<published>2019-04-06T23:09:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=234d6a6e8a4f73ddea627dd4fd78dfb4a91d5a83'/>
<id>234d6a6e8a4f73ddea627dd4fd78dfb4a91d5a83</id>
<content type='text'>
Until now, for short files, we only had a license notice, not an actual
copyright notice. With this commit, a copyright notice has also been
added. We use this new command to find these files, suggested by
`ineiev@gnu.org'.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Until now, for short files, we only had a license notice, not an actual
copyright notice. With this commit, a copyright notice has also been
added. We use this new command to find these files, suggested by
`ineiev@gnu.org'.
</pre>
</div>
</content>
</entry>
<entry>
<title>Imported work on adding Cython and Python's pkgconfig module</title>
<updated>2019-04-05T16:28:16+00:00</updated>
<author>
<name>Mohammad Akhlaghi</name>
<email>mohammad@akhlaghi.org</email>
</author>
<published>2019-04-05T16:28:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=6432d6ef0b33e9ec7b9ec443e8275c0bd4f63245'/>
<id>6432d6ef0b33e9ec7b9ec443e8275c0bd4f63245</id>
<content type='text'>
This work is now merged, I just added the new argument to the `pybuild'
function.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This work is now merged, I just added the new argument to the `pybuild'
function.
</pre>
</div>
</content>
</entry>
<entry>
<title>Python cython and pkgconfig packages added for h5py</title>
<updated>2019-04-05T09:50:06+00:00</updated>
<author>
<name>Raul Infante-Sainz</name>
<email>infantesainz@gmail.com</email>
</author>
<published>2019-04-05T09:50:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=43ffe3bd4a89ee9377fea170a9d9d26cb38cc3dd'/>
<id>43ffe3bd4a89ee9377fea170a9d9d26cb38cc3dd</id>
<content type='text'>
After trying to set the pipeline from scratch with no internet conection
(but all tarballs already downladed), `h5py' Python package complained
about not having access to download `pkgconfig'. After solving this
dependency, it also complained about not having `cython'.

With this commit, we add `pkgconfig' (Python) and `cython' to the
pipeline in order to be able to install `h5py' properly.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
After trying to set the pipeline from scratch with no internet conection
(but all tarballs already downladed), `h5py' Python package complained
about not having access to download `pkgconfig'. After solving this
dependency, it also complained about not having `cython'.

With this commit, we add `pkgconfig' (Python) and `cython' to the
pipeline in order to be able to install `h5py' properly.
</pre>
</div>
</content>
</entry>
<entry>
<title>Dependency version LaTeX macros written at the end of configure</title>
<updated>2019-04-04T20:13:52+00:00</updated>
<author>
<name>Mohammad Akhlaghi</name>
<email>mohammad@akhlaghi.org</email>
</author>
<published>2019-04-04T20:13:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=ac439cf62255ab38da940eb7bba0ccc00fc835f2'/>
<id>ac439cf62255ab38da940eb7bba0ccc00fc835f2</id>
<content type='text'>
Until now, these versions were written in each run. This was mainly
inherited from the old days of the pipeline, where we didn't know the
software on the host. But now that we have almost everything under control,
we can just write these LaTeX macros at the end of the configure script and
make `initialize.mk' simpler and also (very slightly!) speed-up/simplify
the processing.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Until now, these versions were written in each run. This was mainly
inherited from the old days of the pipeline, where we didn't know the
software on the host. But now that we have almost everything under control,
we can just write these LaTeX macros at the end of the configure script and
make `initialize.mk' simpler and also (very slightly!) speed-up/simplify
the processing.
</pre>
</div>
</content>
</entry>
<entry>
<title>Copyright notice on some of the new files</title>
<updated>2019-04-04T18:11:30+00:00</updated>
<author>
<name>Mohammad Akhlaghi</name>
<email>mohammad@akhlaghi.org</email>
</author>
<published>2019-04-04T18:11:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.maneage.org/project.git/commit/?id=2d75d867e638ef95d7d05c5a05cf1a372be50c82'/>
<id>2d75d867e638ef95d7d05c5a05cf1a372be50c82</id>
<content type='text'>
The new files that were just added didn't have a copyright. One has been
added for them with this commit.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The new files that were just added didn't have a copyright. One has been
added for them with this commit.
</pre>
</div>
</content>
</entry>
</feed>
