Daemon News Ezine BSD News BSD Mall BSD Support Forum BSD Advocacy BSD Updates

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

Re: Eclipse CDT 2.0 port



Jeremy Faulkner wrote:
Submitted for testing. The Eclipse 3 port needs to have its package name adjusted to indicate which WS is being used to allow plugin ports to use the correct WS. If there are no complaints/comments/etc. by the end of the week I will send-pr this port.

http://www.gldis.ca/gldisater/eclipse-cdt.tar.gz

Nice work, thanks. Some observations:

- You would probably want to change the runtime dependency from eclipse-3 to eclipse, since when the port is updated it would have the same name.

- Perhaps you would consider performing the same gymnastics that we perform in the eclipse port for JDT, i.e. substitute "linux" for "freebsd". You only need to bring along a largish chunk of eclipse/scripts/configure and fix the pkg-plist accordingly.

- There are erroneous version numbers in pkg-plist that refer to the 1.2.0 version, despite having installed the 2.0 version. You can verify this by observing 'make deinstall' fail. The method I used to create the pkg-plist contents for eclipse is something along these lines (from memory):
# make install
# cd /usr/local
# find eclipse -type f | sort > /tmp/pkg-plist
# find eclipse -type d | sort -r > /tmp/plist.d
# sed -e "s/^eclipse/@dirrm eclipse/g" < /tmp/plist.d >> /tmp/pkg-plist

- In pkg-plist you hard-code the gtk versions regardless of the user's choice while building the port. You may look for an alternative in the eclipse port where there are PLIST_SUB directives for stuff like that. While you are there, why not do the same automation for the version number in order to minimize future port updates?

Ain't porting fun? :-)

Cheers,
--
Panagiotis Astithas, PhD
R&D Manager
EBS, Electronic Business Systems Ltd.
18 Evgenidou Street, 115 25, Athens GREECE
Phone: +30 210 674 7631
Fax: +30 210 674 7601
http://www.ebs.gr