In regards to ticket #18325.
What should be done when a portfile is submitted three times --- one
for each version of python (24, 25, 26), using its respective
PortGroup? The only difference between the versions are four lines:
PortGroup, name, depends_lib, and a post-destroot move.
I
the machine command:
machine
i486
machine
ppc7450
also, running file on the binaries will tell you what architectures
are inside:
file `whereis ls`
/bin/ls: Mach-O universal binary with 2 architectures
/bin/ls (for architecture i386):Mach-O executable i386
/bin/ls (for architecture
I have two question to pose this morning; hope you don't need too much
coffee to respond coherently!
Question 1: Why do launchd startup items use daemondo?
Question 2: Is it frowned upon to include launchd plist files that
don't use daemondo?
Thanks!
smime.p7s
Description: S/MIME
There's a python portfile that is installing docs in an inappropriate
location. It seems the installer merely mimics the directory
structure from the port's download (as detailed by documentation_path
= 'docs/_build/html' in setup.py --- which I assume is getting used).
Do we have a
Can you use reinplace for this?
reinplace s|FIND|REPLACE|[g]
it's driven by sed...
On Feb 9, 2009, at 3:21 PM, Bradley Giesbrecht wrote:
Does anyone know a simple way to env alias a command like
mysql_config=/opt/local/bin/mysql_config5?
I have a lib I'm porting libzdb that uses
Hypothetical addition to port graphviz:
if {${os.platform} == darwin} {
if {${os.major} = 9} {
suggest_supplements-append port:graphviz-gui
} else {
suggest_supplements-append port:graphviz-oldgui
}
}
Hypothetical additions to port graphviz-oldgui:
if {${os.major} =
Hypothetical addition to port graphviz:
if {${os.platform} == darwin} {
if {${os.major} = 9} {
suggest_supplements-append port:graphviz-gui
} else {
suggest_supplements-append port:graphviz-oldgui
}
}
Hypothetical additions to port graphviz-oldgui:
if {${os.major} = 9} {
On Feb 10, 2009, at 5:58 AM, Thomas de Grivel wrote:
2009/2/9 Ryan Schmidt ryandes...@macports.org:
On Feb 8, 2009, at 21:24, Thomas de Grivel wrote:
and propose building (or even rebuilding) ports with more sensible
variants according to installed ones ?
Could you elaborate or give an
On Feb 10, 2009, at 9:22 AM, Vincent Lefevre wrote:
Would running into collisions be easily solved with that we
recommend
messages? For example, some program may want PHP +apache2 and
another
could want PHP +no_web.
One should never recommend a port with a negative variant. This
does not
I'm presently working with a portfile that has lots of values defined
by the submitted --- mostly set to defaults. It also seems that all
dependents are missing (though apple's built-in stuff will end up
satisfying it's needs, it seems).
http://trac.macports.org/ticket/17900
Anywho, the
On Feb 10, 2009, at 5:03 PM, Bryan Blackburn wrote:
On Tue, Feb 10, 2009 at 01:35:12PM -0800, s...@macports.org said:
Revision: 46699
http://trac.macports.org/changeset/46699
Author: s...@macports.org
Date: 2009-02-10 13:35:11 -0800 (Tue, 10 Feb 2009)
...
Added Paths:
---
The demo variant is the only binary-producing portion of that port;
the rest are a series of header files and hooks for ruby.
Do you still feel the demo variant should be phased in since it's
easily built?
On Feb 10, 2009, at 6:18 PM, Ryan Schmidt wrote:
The demos variant says it installs
I've got a few more questions relevant to wikkawiki's portfile.
There's a post-activate section to show a ui_msg, should that just be
post-destroot?
Also, can xinstall replace the following line from the destroot phase?
#file attributes ${wikkapath}/wikka.config.php -permissions 0666
variant use_osx_docroot conflicts php5 mysql5 requires nodeps
description {Create link in /Library/WebServer/Documents} {
post-destroot {
xinstall -d ${destroot}/Library
xinstall -d ${destroot}/Library/WebServer
xinstall -d ${destroot}/Library/WebServer/Documents
I'm working on creating a new binary installer for pspp (mpkg) but
I've come across a build issue on the 10.4 box. It says symbols are
defined twice, but if I comment them out (and make extern) then the
10.5 box says it's undefined.
Are the variants and patchfile directive meant to work
+configure.args-append ../${distname} \
+-DCMAKE_INSTALL_PREFIX=${prefix} \
+-DCMAKE_OSX_SYSROOT=${sysroot}
Are these lines necessary?
The cmake portgroup already has
-DCMAKE_INSTALL_PREFIX=${prefix}
in configure.pre_args and
-DCMAKE_OSX_SYSROOT=${universal_sysroot}
in
Ticket #16400 is a python2.5 module that I seem to have working on my
dev box but the maintainer is unable to get functioning as well. I
managed to get it working with the addition of the cocoa bindings for
pyobjc.
Can you please take a look at our conversations and port files and
offer
These are linking to edgewall.org presently. anyone able to fix it?
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Oh I'm crazy. I should be using source:path instead of trac:path.
False alarm!
On Feb 19, 2009, at 2:09 PM, Jeremy Lavergne wrote:
These are linking to edgewall.org presently. anyone able to fix it?
smime.p7s
Description: S/MIME cryptographic signature
How do I perform a make -f FILE in MacPorts?
While I don't know if it's the way to do, I presently have this working:
build.cmd cd src make -f makefile.osx
I did it that way because I didn't know how to get -f to work and
build phase was ignoring the fact that I set the worksrcpath
How do I perform a make -f FILE in MacPorts?
try something like this:
build.dir ${worksrcpath}/src
build.args -f makefile.osx
Thanks for the hints: Those got me through the build phase. Doing
the same for the destroot phase got me finished.
Is there a way of combining those 4 lines
While the Guide says these default to ${worksrcpath}, I just saw that
they are only set to the initial value of that variable and not they
were overridden as. I have to do the following to get the expected
results:
# this isn't saved into build or destroot.dir
set worksrcpath
While the Guide says these default to ${worksrcpath}
I am sooo lying. Please ignore me (more than usual)!
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
set worksrcpath ${worksrcpath}/src
${worksrcpath} is not an option and should not be changed. If you
need a
different subdirectory, use the worksrcdir option.
Thanks again for pointing that out. For others who might have this
issue, here are my findings to the solution.
At first, I
What's the policy for updating ports that build in parallel to use
parallel_build yes?
Should tickets be made for ones that are maintained or just slip that
change in (given that you actually can build them in parallel)?
smime.p7s
Description: S/MIME cryptographic signature
port lint --nitpick p5-image-exiftool
--- Verifying Portfile for p5-image-exiftool
Warning: Line 5 should be a newline (after PortGroup)
Error: Portfile parent directory graphics does not match primary
category perl
Error: Portfile directory exiftool does not match port name p5-image-
This project of course requires the ability to depend on specific
version ranges of ports (being able to exclude both too old and too
new), and likewise with variants. There would also need to be a way
to
manage rebuilds when existing software would work with a newer
version,
and you want to
Sounds like a good time to get sqlite support running.
+1
This is a much more manageable task that will have tangible benefits.
Although it'd probably be rolled into something else, because I don't
think it's a whole summer's worth of work - probably a week for a
sufficiently motivated
Any idea when milestone 1.7.1 will be complete?
It seems that all tickets but one are closed, and the last real
activity on it is on the order of months.
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
The 'port list' command has led to much confusion in the past.
For most people it does not do what they expect, as it is listing the
latest version of available ports. For example, 'port list installed'
will not list the installed versions, but the versions available. It
can
also happen that
You are relatively new to the MacPorts community, did you ever look at
the base code?
I am not against you taking part as a mentor, I am just concerned if
you
know enough about MacPorts' base to help a student for a project.
But we
can try to sort that out later, it is also possible to do
I should like to think that we should mimic other port systems ---
what methods do they commonly have available?
But what should 'port list' do in your opinion? We can try to fix the
existing command. But in its current form, it causes too much
confusion.
For port list specifically, I would
For port list specifically, I would expect a listing of package
names and package versions with an indication that it's out of date
--- much like port outdated. I suggest we then throw in an
additional
third column indicating the status of that specific version. Here's
an example:
So you
As for what's confusing, I feel we have too many commands available
that overlap on naming.
No commands overlap on naming. You have to differentiate between
commands and pseudo-ports, which are much more powerful.
Some commands have the same name as a pseudo-port, which is probably
what you
Note that the command echo exists to test such expansions:
port echo depends:expat and 'a*'
Gives you a list of all ports that depend on expat and start with
the
character 'a'.
I'm confused why the user has to come up with all these queries
rather
than just doing:
port list depends:expat
I'm happy for list to be removed. If it stays, its output needs to be
changed so it's clear what it is showing, and so 'list installed' does
something sensible. One possibility would be to have two labelled
columns, one for the available version and one for the installed
versions of each port.
I changed the Portfile according to your suggestions.
The patch is submitted in ticket 18809:
http://trac.macports.org/ticket/18809
The revision on this one should NOT be updated, right?
smime.p7s
Description: S/MIME cryptographic signature
___
I changed the Portfile according to your suggestions.
The patch is submitted in ticket 18809:
http://trac.macports.org/ticket/18809
The revision on this one should NOT be updated, right?
Well, I am not sure. There are changes in the Portfile so I increased
the revision to 1. But for users
But if you are going to run
port install '*abc*'
you don't know to which ports this would expand.
port echo '*abc*'
gives you the expanded list.
So it is really some kind of diagnostic tool. Should 'port echo' also
verify the expanded list?
That sounds like functionality I would expect from
So you would like to do 'port search' and then copy the results by
hand
to another port command?
For more pseudo-port usage, I am running
port -v livecheck maintainer:raimue
on a regular basis to check for updates to any ports I maintain.
I wouldn't necessarily say it was by hand, but I've
I'm attempting to create a universal mpkg for PSPP, however it seems
to contain only the i386 variant of libintl (from gettext). It says
only i386 exists when I run `file libintl.8.dylib`, but if I do it on
the actual builds both versions are present.
Does anyone have any insight as to
When are we going to have the mass ports-upgrade to rid ourselves of
the default values that are going to be there (use_parallel_build
yes)? Is it going to be scripted or will this be left to the
maintainers?
On Mar 18, 2009, at 10:10 PM, j...@macports.org wrote:
Make parallel build
Curiously, why did we not (or have not yet) decided to use
build.parallel to follow what seems to be a build.X pattern? Can
build.jobs not take its place?
On Mar 18, 2009, at 10:10 PM, j...@macports.org wrote:
revision48314author...@macports.orgdate2009-03-18 19:10:17 -0700
(Wed, 18 Mar
If I want to append a space and ampersand at the end of a known line,
what's the way to write this in reinplace?
I tried (without success):
reinplace s|psppire|psppire |g
reinplace s|psppire|psppire\ |g
reinplace s|psppire|psppire\ \|g
Any suggestions?
smime.p7s
Description:
I was perusing Arch's website today and noticed there's a flag
package out-of-date link when you're viewing information about a
package. Is this something we might find worthwhile for MacPorts
since not everything has a livecheck?
I presume it can put a community-initiated flag of might
Were both of those links suppose to be to macports-dev ?
On Mar 24, 2009, at 7:16 PM, MacPorts wrote:
Changed page SummerOfCode by rai...@macports.org from 91.11.216.162*
Page URL: http://trac.macports.org/wiki/SummerOfCode
Diff URL:
Wouldn't it make sense to provide a separate and conflicting whole
port maybe for this hten? I now that seems a bit farfetched, but
I'm trying to understand the implications of an hypothentical
removal of the variant concept altogether, which I would find
quite a clean scenario. I don't see a
Can I get assistance in aisle Python? :-)
The ticket, without the portgroup, looks to violate the tree and go
straight for /Library without the prefix for destroot. To fix this, I
tried adding the python25 portgroup to it, but had to override the
build.cmd and destroot.cmd since it seems
Watch out guys, you two are doing opposites of each other.
We need to decide if we're doing py25-db or py25-pydb.
On Mar 26, 2009, at 3:55 PM, mcalh...@macports.org wrote:
revision48644authormcalh...@macports.orgdate2009-03-26 12:55:35
-0700 (Thu, 26 Mar 2009)Log Message
This port is a
Go with the MacPorts version of openssl: MacPorts is meant to be
entirely self-contained.
On Mar 31, 2009, at 9:58 AM, Anand Buddhdev wrote:
My question is: is it okay for me to specify the port to use the
built-in openssl, or is it better to make the port depend on the
openssl from ports?
Presently, MacPorts doesn't distribute binaries.
Using the MacPorts version of OpenSSL has a licensing problem with
GPL ports, though... When distributing package binaries, that is.
Like http://www.finkproject.org/doc/packaging/policy.php?phpLang=en#openssl
I should think that shouldn't stop us from releasing important updates.
On Apr 2, 2009, at 5:25 AM, Ryan Schmidt wrote:
By all means! :) Maybe not just yet, since we just had 1.7.1.
smime.p7s
Description: S/MIME cryptographic signature
___
I know that your long term goal was to integrate man pages and guide
together. But I didn't know yet that work already started on this.
Now I am looking at the man pages in XML format in doc-new/man/xml/*
which are untouched for over a year now and thus outdated as we
continued to work on
Has anyone else witnessed the default livecheck.regex failing when
using master_sites googlecode?
For me, it looks like there is style info and whitespace breaking the
pattern.
smime.p7s
Description: S/MIME cryptographic signature
___
Are these equivalent?
A.
eval xinstall -m 755 [glob {!${build.dir}/bin/*.dylib}] ${destroot}/$
{vtkExamplePath}/bin
B.
cd ${build.dir}
for f in `find bin \! -name '*.dylib'`; do
cp $f ${destroot}/${vtkExamplePath}/bin
done
The only difference I see is the mode setting.
Feel free to get a
If a port uses Qt 4, should I provide variants for which qt4 (kde,
mac, x11) it uses?
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
The portfile posted in the ticket said it was nomaintainer.
I decided that, rather than dropping it entirely I'd pick it up as an
openmaintainer.
On May 16, 2009, at 8:36 PM, Ryan Schmidt wrote:
On May 16, 2009, at 13:51, s...@macports.org wrote:
Revision: 51041
We're updating the ticket to include the fact that the maintainer has
been out of contact for a very long time (on the order of a year --
there appears to be no ticket for when he was involved in the 1.3.5
update from 11 months ago).
Additionally, he has still not responded to the ticket,
Is it a terrible idea to pop in a second startup item in which will
just instal the clamav startup item? This seems messy to me, but it
also will get the job done.
It would make sense for mysql-server to depend on port:mysql and then
merely be a startup item.
What is the list of ports
Duplication will have to happen on name, desc, long desc, I
assume? Version probably does not matter in any strict sense, as it
is not really downloading anything?
Right
So with +server and +clamav_milter what do you do? I am now seeing
the need for these ports:
clamav - base port,
a new version of mumble is out.
while attempting to use the new version, I found a few problems:
libogg should be added to depends_lib
pre-build phase no longer works (sed string replace of path to Qt)
If I can get some assistance with the Qt portion that would be smashing.
smime.p7s
You need python_select -- it allows you to change which python you use.
On Jun 6, 2009, at 1:09 PM, Bradley Giesbrecht wrote:
What is the macports way to get python26 into my paths?
smime.p7s
Description: S/MIME cryptographic signature
___
http://portmill.florianebeling.com/ is doing a default build for all
ports if I'm not mistaken.
On Jun 6, 2009, at 4:35 PM, Jordan K. Hubbard wrote:
They all kinda worked but not well enough that nobody wanted to
actually host them anywhere since they were more clearly science
I'll take on the rewriting to PHP this summer if it needs to be done.
On Jun 8, 2009, at 7:54 PM, Bryan Blackburn wrote:
Of course it doesn't really lower the barrier if someone knows Rails
but not
PHP, especially when quite a bit of code has already been written.
While
trying to stay
There's a difference between a crash and a failed compilation in that
the system can't just catch it. Apple also pays people to look at
those crash reports.
We're almost entirely unpaid volunteers with a variable body count.
On Jun 8, 2009, at 8:26 PM, Andre Stechert wrote:
If a program
Check out this command for ideas on why prefix isn't working:
./configure --help
If you need to override the configure arguments in MacPorts, that's
done via configure.args-append and configure.args-delete
On Jun 9, 2009, at 1:43 AM, Scott Haneda wrote:
I have the most basic of a port
My apologies: the prefix is located in configure.pre_args. Please try:
configure.pre_args-delete --prefix=/opt/local
I believe you shouldn't need to quote it unless there's a space in it.
On Jun 9, 2009, at 1:54 AM, Scott Haneda wrote:
I tried configure.args-delete, do I have to quote it?
Running `make` is handled by the build phase rather than in configure.
Try removing the `...-append make` and see if it fixes that problem.
On Jun 9, 2009, at 2:12 AM, Scott Haneda wrote:
On Jun 8, 2009, at 10:59 PM, Jeremy Lavergne wrote:
My apologies: the prefix is located
Do you have the path correct for the xinstall?
rbldnsd-0.996b/rbldnsd/rbldnsd
Sounds like one too many rbldnsd, unless it's suppose to be inside a
directory names itself inside the distributed directory.
On Jun 9, 2009, at 2:31 AM, Scott Haneda wrote:
That was my first effort, so I tried to
Most of that functionality can be embedded into javascript, which
avoids putting all the work on the backend dev (C.Florian).
Additionally, there are plenty of people who know Javascript/jQuery --
regardless of Ruby or PHP -- and can add it as a patch.
Just a thought.
On Jun 10, 2009, at
distfiles is this by default:
${distname}${extract.suffix}
distname is this by default:
${name}-${version}
That is, distfiles (defined as the name of the distribution filename,
not including the extract suffix) is
${name}-${version}${extract.suffix}
If that hyphen really is an underscore,
On Jun 10, 2009, at 8:49 PM, Scott Haneda wrote:
1) How do I decide the category, can someone show me a list, and
suggest the correct one for this? I see bind9 is in net, perhaps
this should also be in net?
Yes, this would make sense to be in net and then sysutils
2) Do I really need
If you run these commands, what is the URL it ends up using?
sudo port clean --all rbldnsd
sudo port -d fetch rbldnsd
On Jun 10, 2009, at 9:08 PM, Scott Haneda wrote:
Thanks, so I changed it to:
distname${name}_${version}
I believe that is correct. But now it ignores
In the destroot phase, all paths should be prefaced by ${destroot}
On Jun 10, 2009, at 9:14 PM, Scott Haneda wrote:
destroot {
## These perms are obviously wrong, fix them later
# Install binary
xinstall -m 0755 ${worksrcpath}/${name} ${destroot}${prefix}/sbin
# Install man
3) How do the permissions I chose look in the destroot phase?
Why is the program incapable of installing itself from --prefix=?
I am not that versed in this stuff. I run ./configure and it works,
if I run ./configure with the --prefix is balks at me...
$./configure -help
configure:
Melchior:~ snc$ curl -I trd.no.distfiles.macports.org
curl: (7) couldn't connect to host
On Jun 11, 2009, at 12:43 AM, Ryan Schmidt wrote:
trd.no.distfiles.macports.org does not respond to pings or web
requests. Am I the only one seeing this? I've been experiencing this
for days from
I've reopened the ticket to track these changes.
On Jun 14, 2009, at 9:25 PM, Mike Alexander wrote:
That's fine with me (do any other variants need similar changes),
but someone with commit access will have to make the change.
smime.p7s
Description: S/MIME cryptographic signature
On Jun 17, 2009, at 4:25 PM, David Evans wrote:
The total number of entries in the tree is 2520790 but there are
only 321 unique ports involved. Port glib2 alone appears 14023 times.
So there's a lot of overkill going on here.
I'd have to argue that if you can figure out the unique
epoch 1
On Jun 25, 2009, at 6:39 PM, Darren Weber wrote:
Surely wxWidgets @2.8.10_0 is a higher than @2.8.9_0, but not so
according to `port upgrade -uR outdated`
___
macports-dev mailing list
macports-dev@lists.macosforge.org
Shouldn't -append be used here to avoid overwriting the portgroup
settings for each variable you use?
On Jun 28, 2009, at 7:02 PM, Ryan Schmidt wrote:
On Jun 28, 2009, at 09:31, jamesk...@macports.org wrote:
Ticket #20024
You can also remove these lines from the portfile now, since the
PortIndex -- from my experience -- merely gives MacPorts the names and
locations of ports available, as well as very basic information for
search (such as description).
I'm fairly certain the dependencies are calculated from the portfiles
themselves. Anyone else?
On Jun 30, 2009, at
Well, there it is in the PortIndex. dependencies.
On Jun 30, 2009, at 4:27 PM, David Evans wrote:
Ok, so I'm assuming that you mean that it will be updated when
PortIndex is updated. That is, this command uses
the dependency information in PortIndex not from the Portfiles
themselves?
And if ^a gets in your way for jumping in shells, you can change it to
be ^b in the config.
Additionally, ^a ESC works for scrollback.
On Jul 10, 2009, at 3:22 PM, William Siegrist wrote:
CTRL-a [
smime.p7s
Description: S/MIME cryptographic signature
Also took openmaintainership.
On Jul 11, 2009, at 2:45 PM, s...@macports.org wrote:
Modified: trunk/dports/mail/imap-uw/Portfile (53677 = 53678)
--- trunk/dports/mail/imap-uw/Portfile 2009-07-11 18:36:53 UTC (rev
53677)
+++ trunk/dports/mail/imap-uw/Portfile 2009-07-11 18:45:33 UTC (rev
I'm going to say I accidentally commented it prior to simply marking
it in variants.conf on my system. A change to re-enable it is
forthcoming :-)
On Jul 12, 2009, at 10:33 PM, Wesley Moore wrote:
I use dnsmasq on my home network for dhcp and dns. I've noticed that
a startup item is no
We've had a ticket (#20278) come in about the web site once again.
Previously, to our chagrin the XHTML broke in IE7 (#14062).
I'd like to point out that using XHTML was a somewhat divergent path
from HTML. With the advent of HTML 5, we find ourselves once again
returning to the HTML
I'd suggest using the HTML 5 doctype so it's ready to go in the
future, but essentially using HTML 4.01 transitional.
On Jul 14, 2009, at 2:39 AM, Ryan Schmidt wrote:
I have not kept up with the developments of HTML 5 except for the
canvas tag. Is there a specific feature of HTML 5 you
On Jul 14, 2009, at 6:40 AM, Joshua Root wrote:
On 2009-7-14 08:31, Jeremy Lavergne wrote:
I'd like to point out that using XHTML was a somewhat divergent path
from HTML. With the advent of HTML 5, we find ourselves once again
returning to the HTML side of things.
On the other hand: XHTML5
Future work? I wonder, what were the advantages of going with XHTML
to begin with?
On Jul 14, 2009, at 6:57 AM, Joshua Root wrote:
A move for which you still haven't mentioned any specific advantages.
smime.p7s
Description: S/MIME cryptographic signature
On Jul 14, 2009, at 3:01 PM, Scott Haneda wrote:
I am not seeing a port for memtester.
# $Id$
PortSystem 1.0
namememtester
version 4.0.8
categories sysutils
maintainers hostwizard.com:scott
description A userspace utility for testing
Ooo! you use dropbox! /drool
On Jul 14, 2009, at 3:43 PM, Scott Haneda wrote:
http://dl.getdropbox.com/u/340087/Drops/07.14.09/memtest-4460164b-123912.txt
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
On Jul 14, 2009, at 3:43 PM, Scott Haneda wrote:
My plan was to infact xinstal the files, but I am open to learning
how to patch the makefile.
In this one, do I need to just reinplace
INSTALLPATH = /usr/local
Here is the makefile
I don't seeing using HTML 5 as an upgrade so much as a side step. It
doesn't break things -- even as far back as IE6, which most companies
use.
Also, since yet another ticket has shown up due to having to do fun
fancy tagging due to the XML side of XHTML, I figured it would be
another
You just tell it what phase you want it to do, and then it'll stop
after it.
`sudo port patch memtester`
fetch - extract - patch - configure - build - test? - destroot -
install - activate
It's on the Guide if you need a precise listing.
On Jul 14, 2009, at 3:58 PM, Scott Haneda wrote:
There's also -k (keep mode) which should counteract the default to
autoclean.
On Jul 14, 2009, at 3:58 PM, Scott Haneda wrote:
Ok, working on it. How do you test this as you go, and tell ports
to not clean up the files, so I can see if the reinplaces worked to
my liking?
smime.p7s
On Jul 14, 2009, at 4:14 PM, Scott Haneda wrote:
Is this an issue wrt to the mkdir? Should I change that as well?
You wouldn't make it past your pre-patch if that were the case. It
would error out saying it couldn't find the file.
install: all
mkdir -m 755 -p
On Jul 15, 2009, at 2:38 PM, Scott Haneda wrote:
Can someone summarize why some sources are so simple to make a
portfile for, and others require reinplacing the Makefile to alter
it just enough to conform how MacPorts will need it to be?
99% of the time, --prefix works fine, why would
On Jul 15, 2009, at 2:46 PM, Jeremy Lavergne wrote:
If you're going to install these outside of MacPorts, I'd suggest /
usr/local/bin
... for the binaries. basically, you'd mimic macports in that $
{prefix} would be `/usr/local`
smime.p7s
Description: S/MIME cryptographic signature
On Jul 15, 2009, at 2:58 PM, Scott Haneda wrote:
sudo port -d dmg memtester
...
Is there a way on the command above to alter prefix for the one time
build to /usr/local/bin and is there a way to also alter it to be
able to put the man page in the correct place?
Or do I just create a
That shouldn't hurt until 1.8 is out.
Yes we should fix it, but is setting subfolders to 644 helping? We
might run two find commands to set the permissions: 755 everything and
644 non-directories.
Or am I missing an obvious command?
On Jul 16, 2009, at 10:08 PM, Ian Eure wrote:
The
1 - 100 of 1203 matches
Mail list logo
