Bugzilla Bug 3818

This is an ebuild for GNU prolog (gprolog).  This prolog system is ISO 
compliant and has an added finite domain constraint solving system. 
 
There are several web sites for gprolog.  The sourceforge site seems to be 
partially abandoned.  The GNU site (www.gnu.org/software/prolog/prolog.html) 
seems authoritative. 
 
I suggest this go in dev-lang/gprolog.  It has no special dependencies for 
building or running. 
 
Regards, 
Mark 
 
PS There was a small problem with the getting the text files in place.  I 
abandoned trying to do it (they aren't that useful to me) but the sed part is 
commented out in the ebuild.  However, the location I choose for them wasn't 
created at the right time and I didn't feel like fixing that.  Basically, a 
small reordering in the makefile will get those text files installed also.  
Also, I performed a small hack to get the Makefile.in --> Makefile playing 
nicely with DISTDIR.  This may be too kludgeish.

Created an attachment (id=1571) [details]
An ebuild for gprolog-1.2.13, the GNU prolog system

the ./configure statement seems to be just plain wrong to me


fenner, I would suggest using econf and einstall instead of the stuff you have
done.  And the sed'ing really should not be necessary.  Either way, please
submit an ebuild that can be universally used before we can expect any developer
to act on it.

I'm not an enormous fan of the ./configure line; however, this is the way the 
gprolog make process expects to find out about the directories.  Adding DESTDIR 
seems twice as ugly, but it sets up the Makefile properly. 
 
The sed line is necessary to prevent some (non-essential) text files from being 
placed in the /usr directory.  I don't feel the need to spend extra hours 
getting these files in the right spot.  Someone who would like them that badly 
can do it.  These files include ChangeLog, NEWS, COPYING, and one or two 
others.  They are not essential.  
 
Unfortunately, I've never heard of econf or einstall.  I haven't seen them in 
any ebuilds either. 
 
I'm a little confused as to the "universally used".  The program is configured, 
built, and installed with all documentation.  Anyone wishing to use prolog 
(gprolog) on their machine can make use of this script.  The files are in the 
proper locations. 
 
It would be quite a shame for me to have to post this ebuild on a webpage so 
that others can make use of it (when they would likely never look for it). 
 
Regards, 
Mark 
 

I'll start on this soon.

 *ping*  Just seeing if this is under active eyes or not. 

Yes, still working on this.

I've run it through our new, automated ebuild submission frontend, and it
doesn't pass. I've purposely not fixed the flaws myself, as I need some eyes
external to the project to give feedback on the new submission system.

This ebuild was selected as it seemed likely I'd get sensible feedback from you ;)

I'll get back to you with further instructions within the next few days.

Please merge dev-util/lintool and do 'lintool --show-details
gprolog-1.2.13.ebuild '.

It will tell you that there are a few minor issues you have to take care of.
Also, please write a ChangeLog for this, you can check your ChangeLog for
validity by doing 'lintool --show-details --changelog ChangeLog' when you've
written it.

After that, please reopen this bug with a new tarball attached.