taskManeage - Tasks: task #15619, Remove Gnuastro from the default...


You are not allowed to post comments on this tracker with your current authentication level.

task #15619: Remove Gnuastro from the default TARGETS.conf

Submitter:  Boud Roukema <boud>
Submitted:  Mon 27 Apr 2020 03:51:59 PM UTC
Should Start On:  Mon 27 Apr 2020 12:00:00 AM UTC Should be Finished on:  Mon 27 Apr 2020 12:00:00 AM UTC
Category:  Software Priority:  5 - Normal
Status:  Postponed Privacy:  Public
Percent Complete:  20% Assigned to:  None
Open/Closed:  Open Effort:  0.00

Tue 28 Apr 2020 01:50:13 AM UTC, comment #1: 

Thanks for bringing this up Boud, I just pushed a commit to partially address the problem: as described in the message: Astropy is no longer built by default and `TARGETS.conf' has been added to the set of files to be ignored in a merge (and avoid conflicts).

Have you tried the customization checklist in README-hacking.md? I always start new projects by following this list, because I usually forget some points that I have learnt over the years ;-).

I am not yet closing this task because to remove Gnuastro as a default built software, we need to modify the demonstration analysis.

Mohammad Akhlaghi <makhlaghi>
Group administrator
Mon 27 Apr 2020 03:51:59 PM UTC, original submission:  

The present main trunk of maneage has gnuastro and astropy as
targets. While many astronomers working on observational
projects will be happy to have both, many branches of maneage
will most likely be projects with only the minimal additional
packages beyond the basic.mk packages added as targets.
Moreover, many packages will be non-astronomical.

If someone developing a maneage-branched project wishes to update
by merging recent developments from the main maneage trunk to
his/her project, then at the moment, when s/he wishes to do a merge, s/he will have to do a merge of only some of the commits
(git cherry-pick them, for example), carefully avoid merging
the TARGETS.conf file, and also checking various other changes
that might have diverged.

Is it right that the only really annoying divergence that
needs to be checked carefully is TARGETS.conf ?

I'm just thinking aloud here - I haven't tried this yet, but
it would make sense to sooner or later.

Maybe this is already easy - so there may be not much to do
on this task... :)

Boud Roukema <boud>
Group Member


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by makhlaghi (Posted a comment)
  • -email is unavailable- added by boud (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.




    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-04-28 makhlaghi CategoryNone Software
        StatusNone Postponed
        Percent Complete0% 20%
        SummaryLighten the target to encourage branches to merge updates? Remove Gnuastro from the default TARGETS.conf

    Back to the top

    Powered by Savane 3.11