[Bug 220434] [NEW PORT] cad/calculix-cgx: Three-Dimensional Structural Finite Element Program

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220434

--- Comment #11 from Kubilay Kocak <koobs at FreeBSD.org> ---
(In reply to Pedro F. Giffuni from comment #10)

>From what I can see, since calculix-cgx RUN_DEPENDS=ccx:cad/calculix-ccx, all
else being equal (which may not be the case), I would do something similar to
what we did with multimedia/x264, splitting it into cli/library components (the
cli depends on the library). See:
http://svnweb.freebsd.org/changeset/ports/373073

The procedure there was:

1) x264 -> svn cp libx264 (new port)
2) modify x264 to depend on libx264 port
3) make modifications to each to make them 'cli' and 'library' only
respectively
4) commit

Reasons:

- No deprecation/removal/user intervention necessary
- History retained for new port ("came from x264")
- Single/atomic commit

There was however, no renaming of the original port (though after commit it did
much much less). The reason for no rename was users would always only search
for x264 (not x264-cli), and less confusing is better.

With that, your questions:

---------------
Should the original port be moved or copied under each of the new ports?
---------------

Depends. moves are related to renames (not a new port), copies are related to
history (for new ports). 

If a substantial portion of the original port is retained in the new parts,
then:

(A) If calculix can remain named calculix (even if its still "cgx only" build
specific), then you can do:

1) svn cp calculix calculix-ccx
2) update calculix to depend on calculix-ccx
3) modify calculix-ccx to do only ccx things
4) commit

(B) If it should/must be renamed, Id look at:

1) Same as (A) - (commit 1), then
2) svn mv calculix -> calculix-cgx
3) add MOVED entry
4) commit

I don't know if in SVN you can copy a source, and also move the source in a
single commit. E_NEEDSVNEXPERT.

If a substantial portion of the original is *NOT* retained in calculix-ccx:

1) Create a new port (no svn cp, no history)
2) update calculix to depend on calculix-ccx
3) commit

Optionally: do B(2)(3)(4) after. (renaming the original port)

---------------
Can I just remove the old port or should it be labelled "deprecated"?
---------------

In both of the above cases, deprecation isn't necessary, as each option
provides for a 'complete replacement' with a clean user upgrade path as a first
step.  That is, they wont need manual intervention, requiring custom
instructions to migrate in /usr/ports/UPDATING.

-- 
You are receiving this mail because:
You are on the CC list for the bug.