[MacPorts] #26703: gutcheck : NEW

[MacPorts]

#26703: gutcheck : NEW
------------------------------+---------------------------------------------
 Reporter:  oksmith@…         |       Owner:  macports-tickets@…                   
     Type:  submission        |      Status:  new                                  
 Priority:  Normal            |   Milestone:                                       
Component:  ports             |     Version:  1.9.1                                
 Keywords:  textproc          |        Port:  gutcheck                             
------------------------------+---------------------------------------------

Comment(by oksmith@…):

 I am back from vacation and am in complete agreement with your concerns.

 gutcheck doesn't come with any kind of a configuration script--it's just a
 plain old C files as far as the Mac is concerned--so all those extra files
 come from autoconf/automake.  The empty files irritate me too.  But that's
 autoconf/automake.

 I am happy to rework the Portfile.

 I am sure there are other ports that are just plain C files and MacPorts
 manages to install them.  Could you please refer me to a port that you
 think is a good example?  I'm sure I can figure out the rest.

 I look forward to your reply.

 Thanks.


 Replying to [comment:1 ryandesign@…]:
 > I'm uploading a new version of this portfile with these changes:
 >
 >  * [http://guide.macports.org/#development.creating-portfile Added the
 modeline]
 >  * Reformatted / reindented a little, including changing tabs to spaces
 and removing trailing whitespace (see "port lint --nitpick")
 >  * Added license keyword
 >  * Since the distfile name does not contain the version number, I added
 "dist_subdir ${name}/${version}" to [wiki:PortfileRecipes#unversioned-
 distfiles avoid checksum errors later]
 >  * Used "extract.mkdir yes" instead of reimplementing it
 >  * Simplified post-extract by using "xinstall -W"
 >  * Removed "use_configure yes"; that is the default
 >  * Changed post-destroot so documentation files go in
 ${prefix}/share/doc/${name}
 >
 > I'm not committing it yet because I'm concerned about the number of
 files you propose we put in the files directory, including a 164K
 configure script. (Granted that's not a terribly large file, but certainly
 many times the size of a typical portfile, and the portfile and files
 directory gets transferred to every MacPorts users machine, regardless of
 whether they have any interest in gutcheck or not.) Where did these files
 come from? Why is upstream not providing them if they are necessary? Could
 we get by without them? I will admit having a configure script does make
 it easier for the port to build universal and for other build_archs. But
 do we really need all those other files? empty text files? If we could
 generate the configure and Makefile.in by using "use_autoconf yes" for
 example that would be better.

-- 
Ticket URL: <https://trac.macports.org/ticket/26703#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS