[task #15772] R (r-cran) packages in Maneage

[Mohammad Akhlaghi]

Update of task #15772 (project reproduce):

                Category:                    None => Software               
                  Status:                    None => In Progress            
        Percent Complete:                      0% => 80%                    
             Assigned to:                    None => boud                   

    _______________________________________________________

Follow-up Comment #5:

Thanks for all the great work on this Boud!

I rebased the two commits over the 'version-update' branch, but couldn't find
any rules for all the R packages added! Reading through the message of Commit
3ee3e321f6 <https://gitlab.com/maneage/project-dev/-/commit/3ee3e321f6> (hash
after rebasing), I noticed that there is suppose to be a 'r-cran.mk' file that
was apparently forgotten in the commits.

Can you please add the file to this fork of the R branch
<https://gitlab.com/maneage/project-dev/-/tree/R>? 

Also, could you please format the tarballs in the Maneage convention for
longevity (as described in task #15699)? You can use the latest box of code in
that task as the recipe (it is designed to be easily placed into a 'for' loop
and done over many tarballs in cases like this). 

Once the new tarballs are made, you can update the checksums and push them to
a development branch of tarballs-software
<https://gitlab.com/maneage/tarballs-software> project, so I later merge them
in (I have already added you as a "developer", so you can push branches there
and avoid making a large fork!). Keeping a clone of this repository on your
computer is also good to provide as the "software" directory in all your
Maneage'd projects and avoiding to have many copies of the tarballs (symbolic
links are placed in the build directory of each project). Alternatively, you
can put the tarballs in a certain URL that I can pick-up and put in that
repository myself. 

As described in task #15699, it is very important for longevity that we have a
unified format for all the newly added software tarballs ;-)! We can't do
anything for the old ones, but all new ones should have this format.

In the process of re-building the tarballs, I also recommend to standardize
the unpacked directory name to avoid complicating the un-packing+building code
(and further unifying the format of the tarball).

    _______________________________________________________

Reply to this item at:

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

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