I took a look at all the ports that depend on imake and suggest that we remove 
a bunch of them.

These are all 5+ years dead upstream, have no dependents, and don't seem to be 
terribly important:

magicpoint - Upstream development stopped in 2008
tgif - Upstream no longer exists, shipped version was released in 2001
rasmol - Packaged version released in 2008, latest release was in 2009
canna - Last updated in 2004
emiclock - No upstream any more
fvwm - Last updated in 1995, replaced by fvwm2
kinput2 - Last updated in 2001
kxterm - No upstream any more
sunclock - No upstream any more
vtwm - Last updated in 2004
wmclock - No upstream any more
xcb - No upstream(?), upstream 505s, port last updated in 2009
xearth - Last updated in 1999
xmove - Last updated in 1997
xsnow - Last updated in 2001
xspringies - No upstream, older than 1998
xtu - No upstream

KDE 3 was last released in 2008, and I think we should probably remove it 
seeing as how upstream is now focused mainly on development of KDE 5.  I highly 
doubt kde3 even builds on modern systems since I don't think qt3 does...
kdebase3 - Released in 2008

For these last two (transfig and xfig are basically the same), we should 
probably try to fix them by working with upstream to move to a newer build 
system:
transfig
xfig
tightvnc

If I hear no objections in the next few days, I'll remove the ports in that 
first group.  If nobody speaks up, I think we should nuke KDE3 in a few weeks.

--Jeremy

> On Sep 28, 2014, at 17:42, Jeremy Huddleston Sequoia <[email protected]> 
> wrote:
> 
> Why don't we just remove xorg-cf-files, imake, and all dependent ports?  
> Obviously any project still using imake a decade after the build system was 
> declared dead are themselves not well maintained projects and I argue should 
> not be in our port repository.
> 
> These are the ports that depend on the archaic build system:
> 
> spim
> ivtools
> magicpoint
> tgif
> xfig
> kdebase3
> transfig
> arb
> rasmol
> openvas-server
> canna
> emiclock
> fvwm
> kinput2
> kxterm
> sunclock
> tightvnc
> vtwm
> wmclock
> xcb
> xearth
> xmove
> xsnow
> xspringies
> xtu
> 
> --Jeremy
> 
>> On Sep 27, 2014, at 19:15, Ryan Schmidt <[email protected]> wrote:
>> 
>> I'm going to try to work on the imake problem, specifically that ports using 
>> imake fail with Xcode 5 and up because they require a cpp with traditional 
>> cpp support which clang doesn't have. 
>> 
>> In the process I plan to create an xmkmf portgroup to replace the use_xmkmf 
>> keyword in base. 
>> 
>> My proposal is to have this portgroup depend on the latest stable gcc port 
>> (currently gcc49) and have it use its cpp in IMAKECPP when the Xcode version 
>> is 5 or greater. I tried this with one port already and was able to build it 
>> on Yosemite beta. 
>> 
>> Let me know if you have any objections to this proposal or if you have other 
>> ideas how to solve this problem.
>> 
>> 
>> _______________________________________________
>> macports-dev mailing list
>> [email protected]
>> https://lists.macosforge.org/mailman/listinfo/macports-dev
> 
> _______________________________________________
> macports-dev mailing list
> [email protected]
> https://lists.macosforge.org/mailman/listinfo/macports-dev

_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to