June 2008 - macports-tickets - lists.macosforge.org

[MacPorts] #15784: MacPorts Guide, PortGroup perl5: need to document perl5.use_module_build
by MacPorts 25 Sep '14

25 Sep '14

#15784: MacPorts Guide, PortGroup perl5: need to document perl5.use_module_build ----------------------------------------------+----------------------------- Reporter: stolen-from-macports-trac(a)l2g.to | Owner: jmpp(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Website & Documentation Component: website | Version: 1.6.0 Keywords: | ----------------------------------------------+----------------------------- http://guide.macports.org/#reference.portgroup.perl The documentation ought to mention the perl5.use_module_build keyword, specific to the perl5 PortGroup. This is used for Perl modules that require Module::Build. -- Ticket URL: <http://trac.macports.org/ticket/15784> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15625: Guide doesn't explain variants very well
by MacPorts 25 Sep '14

25 Sep '14

#15625: Guide doesn't explain variants very well -------------------------------------+-------------------------------------- Reporter: myrrhlin(a)gmail.com | Owner: markd(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.6.0 Keywords: doc variants guide wiki | -------------------------------------+-------------------------------------- There are some obvious questions about variants which are not answered in the guide (and also not in the FAQ). I only began to figure out the answers by trying things and finding out what worked and what didn't. The guide should be expanded to answer these questions. * Can multiple variant options be selected at install time? (yes) * Do variant options sometimes conflict, and how would I know? (??) * Can two variants be installed at the same time? (yes, but only one can be active at a given time. use port deactivate on the first variant, then install the second) * Can an existing variant be modified to add or remove variant options? (no) * What if I need to add a new option to a variant (or remove one)? (uninstall it, then reinstall with the desired options) * Is the 'universal' variant considered to be exclusive of all other options? That is, if there is an option that enables liba52 support, am I to assume the universal install doesn't have this support? (??) * The documentation mentions turning off 'default' variant options with the minus sign syntax -- how do I find out which are the default ones, if any (other than reading the portfile)? (??) I might add that the short descriptions of the variants are quite unclear to me, and insufficient. They're the sort of description which are adequate if you already know what the options mean. If you don't, it doesn't help much in making wise choices. I hope you consider support for greater documentation of these choices in the portfiles or elsewhere, more than a fraction of a line. The wiki would also be a great place for further documentation of this kind, if it was expanded to include pages for every port with variants. Please make it easier somehow for the documentation of variants to be expanded. Here's an example. Whats the difference between darwin7, darwin8, macosx options as opposed to universal? I know 10.4 is darwin 8 (you should explain that too), but just when do I need to specify that? Anytime I see it given as a variant? Are darwin7 and darwin8 exclusive? Are darwin8 and macosx exclusive? How would I know? Another example. I see that ffmpeg includes native support for vorbis and xvid, but there are variant options to use external libraries instead. What are the advantages to each choice? Which provides greater speed/flexibility/etc? -- Ticket URL: <http://trac.macports.org/ticket/15625> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15623: guide (trunk) Documentation missing for several Tcl extenstions (pextlib1.0)
by MacPorts 25 Sep '14

25 Sep '14

#15623: guide (trunk) Documentation missing for several Tcl extenstions (pextlib1.0) -----------------------------------+---------------------------------------- Reporter: febeling(a)macports.org | Owner: markd(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Website & Documentation Component: guide | Version: 1.6.0 Keywords: | -----------------------------------+---------------------------------------- Many of the Pextlib commands are undocumented, among them prominent ones like "system". {{{ system flock readdir strsed mkstemp mktemp md5 fs-traverse filemap rpm-vercomp rmd160 sha1 compat umask sudo mkfifo unixsocketpair mkchannelfromfd pipe curl symlink unsetenv readline rl_history getuid geteuid getgid getegid setuid seteuid setgid setegid name_to_uid uid_to_name name_to_gid gid_to_name tracelib }}} See the definition of the extension here: http://trac.macports.org/browser/trunk/base/src/pextlib1.0/Pextlib.c#L1167 The list is compiled by copying those minus the ones which actually are documented here in the guide. http://guide.macports.org/#reference.tcl-extensions Not sure if some of these should stay undocumented because they are rather implementation detail or "private", but most look quite generally applicable. The related list discussion was this: http://www.mail-archive.com/macports- dev(a)lists.macosforge.org/msg05179.html -- Ticket URL: <http://trac.macports.org/ticket/15623> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15518: snort-2.6.1.5 patches to add postgresql83 variant
by MacPorts 25 Sep '14

25 Sep '14

#15518: snort-2.6.1.5 patches to add postgresql83 variant ---------------------------------------+------------------------------------ Reporter: adioso(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Keywords: snort 2.6.1.5 postgreql83 | ---------------------------------------+------------------------------------ Here are 2 patches to add a postgresql83 variant. This is my first ticket so I hope I have everything correct. These patches were created against 1.6.0. -- Ticket URL: <http://trac.macports.org/ticket/15518> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15514: reinplace should warn if nothing got replaced
by MacPorts 30 Aug '14

30 Aug '14

#15514: reinplace should warn if nothing got replaced -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: base | Version: 1.6.0 Keywords: | -------------------------------------+-------------------------------------- What's always bugged me about reinplace is that you get no notification if nothing got replaced, which will probably bite you later. If you use a patchfile to modify a file, and the patch is out of date, the patch fails to apply and the port command exits with an error. This is good; it alerts the port author to the situation and they can fix it by changing or removing the patch. But with reinplace, if the underlying file you're modifying has changed such that the reinplace no longer causes anything to change, you get no warning and the port command proceeds. I think the correct behavior might ultimately be to error out entirely if a reinplace doesn't change a file, just like we do with failed patches. But as a first step, to get port authors used to this change, it might be friendlier to just print a warning for now. The attached patch adds a warning if a reinplace doesn't change the underlying file. -- Ticket URL: <http://trac.macports.org/ticket/15514> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 19

[MacPorts] #15692: New port: Freenet
by MacPorts 05 Apr '14

05 Apr '14

#15692: New port: Freenet --------------------------------------------------+------------------------- Reporter: dbonde+bugs+macosforge.org(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | --------------------------------------------------+------------------------- Please include a freenet port. -- Ticket URL: <http://trac.macports.org/ticket/15692> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15648: VPython request
by MacPorts 27 Feb '14

27 Feb '14

#15648: VPython request -------------------------------+-------------------------------------------- Reporter: ralph(a)cs.cf.ac.uk | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Requests Component: ports | Version: 1.6.0 Keywords: VPython | -------------------------------+-------------------------------------------- Any chance of a MacPort of VPython? -- Ticket URL: <http://trac.macports.org/ticket/15648> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 21

[MacPorts] #15571: request - uniform Portfile standard to handle the different possibilities of Fortran compilers
by MacPorts 29 Jan '14

29 Jan '14

#15571: request - uniform Portfile standard to handle the different possibilities of Fortran compilers -------------------------------------+-------------------------------------- Reporter: davidh(a)ipac.caltech.edu | Owner: markd(a)macports.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.6.0 Keywords: | -------------------------------------+-------------------------------------- I don't write code in Fortran, but some of the ports I use require Fortran. Different Portfiles depend on different Fortran compilers. Contrast fftw-3(g95, gfortran/gcc4.2, gfortan/gcc4.3) pgplot(g77 on PPC, gfortran/gcc4.2 on i386) and cfitsio(gfortran/gcc42). There are at least 4 compilers to choose from. My request: formulate a standard to allow any of the compilers to be selected with a variant. The fftw-3 Portfile comes closest with variants to select any one of 3 compilers. If possible, I'd like to see g77 deprecated. -- Ticket URL: <http://trac.macports.org/ticket/15571> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #15653: std::locale broken in gcc
by MacPorts 27 Nov '13

27 Nov '13

#15653: std::locale broken in gcc --------------------------------+------------------------------------------- Reporter: dirk(a)code-shop.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- When compiling the following code: #include <locale> #include <iostream> #include <exception> #include <clocale> void try_c_locale(const char* locale_name) { if( std::setlocale(LC_ALL, locale_name) == NULL ) printf("Failed to setlocale(LC_ALL, \"%s\")\n", locale_name); else printf("Succeeded in calling setlocale(LC_ALL, \"%s\")\n", locale_name); } void try_cpp_locale(const char* locale_name) { try { std::locale my_locale(locale_name); } catch(std::exception& e) { printf("Failed ctor for std::locale with \"%s\": %s\n", locale_name, e.what()); return; } printf("Succeeded ctor for std::locale with \"%s\"\n", locale_name); } int main(void) { // Some locales from "locale -a" on my OS X system, here is proof // that these locales do exist on my system. Take my word for it // that "locale -a" also shows these locales existing on my linux // system as well. // // rutski@imac:~$ locale -a | tail -n 2 // C // POSIX // rutski@imac:~$ locale -a | grep en_US // en_US // en_US.ISO8859-1 // en_US.ISO8859-15 // en_US.US-ASCII // en_US.UTF-8 // rutski@imac:~$ locale -a | grep pl_PL // pl_PL // pl_PL.ISO8859-2 // pl_PL.UTF-8 // rutski@imac:~$ const char* test_locales[] = { "C", "POSIX", "en_US", "en_US.UTF-8", "pl_PL", "pl_PL.ISO8859-2" }; printf("Trying c locales...\n"); for(size_t x = 0; x < sizeof(test_locales)/sizeof(char*); x++) try_c_locale(test_locales[x]); printf("\n"); printf("Trying C++ locales...\n"); for(size_t x = 0; x < sizeof(test_locales)/sizeof(char*); x++) try_cpp_locale(test_locales[x]); } the output clearly states there is something wrong: Trying c locales... Succeeded in calling setlocale(LC_ALL, "C") Succeeded in calling setlocale(LC_ALL, "POSIX") Succeeded in calling setlocale(LC_ALL, "en_US") Succeeded in calling setlocale(LC_ALL, "en_US.UTF-8") Succeeded in calling setlocale(LC_ALL, "pl_PL") Succeeded in calling setlocale(LC_ALL, "pl_PL.ISO8859-2") Trying C++ locales... Succeeded ctor for std::locale with "C" Succeeded ctor for std::locale with "POSIX" Failed ctor for std::locale with "en_US": locale::facet::_S_create_c_locale name not valid Failed ctor for std::locale with "en_US.UTF-8": locale::facet::_S_create_c_locale name not valid Failed ctor for std::locale with "pl_PL": locale::facet::_S_create_c_locale name not valid Failed ctor for std::locale with "pl_PL.ISO8859-2": locale::facet::_S_create_c_locale name not valid a google serach delivers this: http://groups.google.com/group/gnu.gcc.help/browse_thread/thread/99d874aed6… appearantly, a --enable-clocale to configure might do something however, macport's configure stage does not allow for adding options (or I could not find it) * could this be fixed in gcc? (in libstdc++) * could this be added to macport (adding extra configure options) -- Ticket URL: <http://trac.macports.org/ticket/15653> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #15432: Update mod_security
by MacPorts 23 Nov '13

23 Nov '13

#15432: Update mod_security -----------------------------------+---------------------------------------- Reporter: webmaster(a)lifedit.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: High | Milestone: Port Updates Component: ports | Version: 1.6.0 Keywords: mod_security | -----------------------------------+---------------------------------------- Hi ... I would like to see an update to the latest release of mod_security for Apache. Current MacPort version is 1.8.6 (http://trac.macports.org/browser/trunk/dports/www/mod_security/Portfile) and the official project website (http://www.modsecurity.org) currently shows version 2.5.6 to download (http://www.modsecurity.org/download/direct.html) So I think it would be great if this one could be updated soon if possible. Thanks! -- Ticket URL: <http://trac.macports.org/ticket/15432> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9