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

[MacPorts] #16355: Document port dir, port file, port edit in the Guide
by MacPorts 25 Sep '14

25 Sep '14

#16355: Document port dir, port file, port edit in the Guide -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: markd(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Website & Documentation Component: guide | Version: Keywords: | -------------------------------------+-------------------------------------- The Guide should explain `port dir`, `port file` and `port edit` The manpage (`man port`) does explain these. A good place for this might be in the [http://guide.macports.org/#development.patches.portfile Portfile Patches section]. There, we tell the user to copy the Portfile and then edit it, but we never tell the user where the Portfile is so that they can accomplish this. -- Ticket URL: <http://trac.macports.org/ticket/16355> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #15819: Add a pointer to 7.2 in 4.2 and/or 4.6
by MacPorts 25 Sep '14

25 Sep '14

#15819: Add a pointer to 7.2 in 4.2 and/or 4.6 --------------------------------+------------------------------------------- Reporter: ocroquette(a)free.fr | Owner: markd(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- Right now the new port maintainer is not really guided from one step to the other to create a new port, especially the jump to the last one (chapter 7). For people who wants to submit a new portfile from scratch, it would be useful to have a link from 4.2 and/or 4.6. Or may be even a quick howto referencing 4. and 7. -- Ticket URL: <http://trac.macports.org/ticket/15819> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #15818: Describe when to run "portindex"
by MacPorts 25 Sep '14

25 Sep '14

#15818: Describe when to run "portindex" --------------------------------+------------------------------------------- Reporter: ocroquette(a)free.fr | Owner: markd(a)macports.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- Document in 4.2 and 4.6 for which changes to the Portfile re-running portindex is necessary. -- Ticket URL: <http://trac.macports.org/ticket/15818> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[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] #16373: svn fetch type should maintain a persistent working copy
by MacPorts 20 Aug '14

20 Aug '14

#16373: svn fetch type should maintain a persistent working copy -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: base | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- "`fetch.type svn`" is inefficient in that it checks out a new working copy every time, directly to the work area. That would be like a normal port downloading the distfile every time. Instead, we should check out a working copy to that port's distpath, and then in the extract phase we should `svn export` it to the work area. Some checks will be needed in the fetch phase to ensure that an existing working copy: * has no modifications: check `svn status`. Ideally we would try to clean up the working copy, for example by `svn revert`ing modified or added or deleted files, and then in a second `svn status` run, delete any unversioned files. But it's already an improvement if we just discard the working copy if `svn status --ignore-externals` produces any output. * is from the right URL: check `svn info`: check if the "URL" is the one we want. If not, check that the "Repository Root" is a substring of the repository we want. If yes, try to `svn switch` to the URL and revision we want; if not, discard the working copy. So the fetch phase would go something like... {{{ if {working copy exists} { if {working copy has modifications} { delete working copy } } if {working copy exists} { if {working copy url is the one we want} { svn update to the desired revision } else { if {working copy repository root matches beginning of desired url} { try to svn switch to the desired url and revision if {an error occurred} { delete working copy } } else { delete working copy } } } if {working copy doesn't exist} { check out working copy } }}} And the extract phase is simply to `svn export` the working copy from the distpath to the worksrcpath. (There is [http://subversion.tigris.org/issues/show_bug.cgi?id=2429 one problem] if the working copy has externals and the user is using Subversion earlier than 1.5, for example Subversion 1.4.whatever which is included with Leopard. But rather than spend time working around this in base, I think this is a case where the port should depend on MacPorts subversion.) -- Ticket URL: <http://trac.macports.org/ticket/16373> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 21

[MacPorts] #15859: openjade 1.3.2, Revision 2: demo failure
by MacPorts 30 Jul '14

30 Jul '14

#15859: openjade 1.3.2, Revision 2: demo failure -----------------------------+---------------------------------------------- Reporter: tom.duck(a)dal.ca | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: openjade | -----------------------------+---------------------------------------------- Openjade has a demo program that can be used to test the installation. See http://olympus.het.brown.edu/cgi- bin/dwww?type=file&location=/usr/share/doc/openjade#using. Execution of the demo results in a bus error: {{{ $ openjade demo.sgm Bus error }}} This is on my 10.4 Tiger system with the updated openjade port. -- Ticket URL: <http://trac.macports.org/ticket/15859> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7