reproduce-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[task #15855] Build directory with only two subdirectories: analysis/ an


From: Mohammad Akhlaghi
Subject: [task #15855] Build directory with only two subdirectories: analysis/ and software/
Date: Fri, 8 Jan 2021 22:27:53 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0

Update of task #15855 (project reproduce):

                  Status:               Need Info => Done                   
        Percent Complete:                      0% => 100%                   
             Assigned to:                    None => makhlaghi              
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

Since there was no objection to this and two weeks have passed, it has been
implemented in Commit d9a6855948
<http://git.maneage.org/project.git/commit/?id=d9a6855948> and I am closing
this task. 

Converting your analysis scripts to this new feature is very easy and fully
described in the commit message. In case, a project doesn't implement it (and
just re-configures and re-makes from scratch) there should also be no problem
(or crash). The project should build fine if they used '$(texdir)' and not
'$(BDIR)/tex' for example.

Also, the README.md <http://git.maneage.org/project.git/tree/README.md> now
has a section titled "Only software environment in the Docker image" and
describes how to do the proposed solution of the first comment of this task. 

I tested this scenario with a Docker image and it worked very nicely: the
Docker image only has the software environment and nothing else! The project's
source, software tarballs and built analysis outputs are fully shared with the
host OS. So for example people can edit the project in their host OS, and run
it in the Docker image and see the PDF (or created data files) on their own
OS!

When extracting the Docker image as a file and compressing it (as described in
the new section of 'README.md'), the compressed file for the core Maneage
branch was about 800Mb (uncompressed it was about 2GB). 

So it is indeed easy to move this file to another computer that supports
Docker for a fast reproduction of the environment, or more importantly when
there is a bug in building a certain Maneage software on that OS, which hasn't
yet been fixed. The latter was one of the main reasons this was very important
for me.

    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?15855>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]