On Jan 18, 2009, at 4:02 PM, Bradley Giesbrecht wrote:
This is what I do.
http://guide.macports.org/#development.local-repositories
Are there any more specific notes on perl mods, and the perl.sources
file? Mainly, how it works, and what you use as filenames? I am
looking at port edit p
On Jan 18, 2009, at 3:47 PM, Scott Haneda wrote:
Hello, I am back on this again. Had to get a new computer. I
remember I used to do `edit port ASSP` and it would open a file,
that I had done some work on. I have MacPorts installed on my new
machine now, but how do I get the old edited po
Hello, I am back on this again. Had to get a new computer. I
remember I used to do `edit port ASSP` and it would open a file, that
I had done some work on. I have MacPorts installed on my new machine
now, but how do I get the old edited port over to my new machine, so I
can work where I
On Tue, Nov 11, 2008 at 06:08:58PM -0800, Scott Haneda said:
[...]
>
> FYI
> <[EMAIL PROTECTED]>: host delta.macosforge.org[17.254.17.249] said:
> 550 5.1.1
>< [EMAIL PROTECTED]>: Recipient address rejected: User unknown in
> virtual
>alias table (in reply to RCPT TO command)
> Reporting-
On Tue, Nov 11, 2008 at 05:43:54PM -0800, Scott Haneda said:
[...]
>
> But I can create a new port, if I so desired, and call it assp1, and
> submit that? I will not be doing that, but I wanted to make sure I can
> move on and make assp2 as a totally new port.
For ports that make sense, there
On Tue, Nov 11, 2008 at 06:06:17PM -0800, Scott Haneda said:
[...]
>
> I will be happy to write you a short summary. I think the basics of it
> are that it was hard for me to know where to start. Also, consider,
> people like me may want to add ports, but they get stuck on two things,
> learni
On Nov 11, 2008, at 3:56 PM, Ryan Schmidt wrote:
It looks like the previous maintainer was rshaw. That would be
Robert Shaw, according to MacPortsDevelopers:
https://trac.macports.org/wiki/MacPortsDevelopers
You could try emailing rshaw at macports dot org.
FYI
<[EMAIL PROTECTED]>: host d
On Nov 11, 2008, at 5:37 PM, Bryan Blackburn wrote:
On Tue, Nov 11, 2008 at 03:43:26PM -0800, Scott Haneda said:
[...]
Ahh nice, thanks. I am not entirely sure, you guys can be the
gauge of
this, but I feel my questions are not that out of the ordinary for
a new
port maker. I do look at
On Nov 11, 2008, at 4:10 PM, Ryan Schmidt wrote:
On Nov 11, 2008, at 17:43, Scott Haneda wrote:
On Nov 11, 2008, at 1:57 AM, Bryan Blackburn wrote:
On Tue, Nov 11, 2008 at 01:20:51AM -0800, Scott Haneda said:
Hello, had some more spare time this evening, working on the assp
port,
thanks to a
On Nov 11, 2008, at 4:01 PM, Ryan Schmidt wrote:
On Nov 11, 2008, at 17:53, Scott Haneda wrote:
How do you suggest I deal with this port in final release. The old
port was 1.1.0, and ASSP has gone through a directory structure
change, as well as multiple file deletions and additions.
The
On Tue, Nov 11, 2008 at 03:43:26PM -0800, Scott Haneda said:
[...]
>
> Ahh nice, thanks. I am not entirely sure, you guys can be the gauge of
> this, but I feel my questions are not that out of the ordinary for a new
> port maker. I do look at the docs before I ask here, either I am a bad
> se
On Nov 11, 2008, at 17:43, Scott Haneda wrote:
On Nov 11, 2008, at 1:57 AM, Bryan Blackburn wrote:
On Tue, Nov 11, 2008 at 01:20:51AM -0800, Scott Haneda said:
Hello, had some more spare time this evening, working on the assp
port,
thanks to all who are entertaining me in this training proce
On Nov 11, 2008, at 17:53, Scott Haneda wrote:
How do you suggest I deal with this port in final release. The old
port was 1.1.0, and ASSP has gone through a directory structure
change, as well as multiple file deletions and additions.
The 1.4.3.0 is probably the last release before 2.0 co
On Nov 11, 2008, at 17:48, Scott Haneda wrote:
On Nov 11, 2008, at 3:10 AM, Ryan Schmidt wrote:
On Nov 11, 2008, at 03:57, Bryan Blackburn wrote:
On Tue, Nov 11, 2008 at 01:20:51AM -0800, Scott Haneda said:
Since this is just moving files around, I have set
use_configure no
but t
How do you suggest I deal with this port in final release. The old
port was 1.1.0, and ASSP has gone through a directory structure
change, as well as multiple file deletions and additions.
The 1.4.3.0 is probably the last release before 2.0 comes out, which
is in beta now. I can see a bug
On Nov 11, 2008, at 3:10 AM, Ryan Schmidt wrote:
On Nov 11, 2008, at 03:57, Bryan Blackburn wrote:
On Tue, Nov 11, 2008 at 01:20:51AM -0800, Scott Haneda said:
Since this is just moving files around, I have set
use_configure no
but that seems misleading to me, if it is set to no, h
On Nov 11, 2008, at 1:57 AM, Bryan Blackburn wrote:
On Tue, Nov 11, 2008 at 01:20:51AM -0800, Scott Haneda said:
Hello, had some more spare time this evening, working on the assp
port,
thanks to all who are entertaining me in this training process.
I am working on the port as it started, so I
On Nov 11, 2008, at 03:57, Bryan Blackburn wrote:
On Tue, Nov 11, 2008 at 01:20:51AM -0800, Scott Haneda said:
Since this is just moving files around, I have set
use_configure no
but that seems misleading to me, if it is set to no, how come
configure
still gets run?
Since ASSP
On Tue, Nov 11, 2008 at 01:20:51AM -0800, Scott Haneda said:
> Hello, had some more spare time this evening, working on the assp port,
> thanks to all who are entertaining me in this training process.
>
> I am working on the port as it started, so I issue sudo port edit assp.
> If I run:
> clear;
Hello, had some more spare time this evening, working on the assp
port, thanks to all who are entertaining me in this training process.
I am working on the port as it started, so I issue sudo port edit assp.
If I run:
clear; sudo port -d install assp
I generally get a bunch of errors, certainly
On Nov 9, 2008, at 03:57, Scott Haneda wrote:
On Nov 9, 2008, at 1:02 AM, Ryan Schmidt wrote:
You don't need to install any ports; all ports' portfiles are
already on your computer. Just go to the dports directory and grep
through them. Portfiles are always in a directory for the port,
w
On Nov 9, 2008, at 1:02 AM, Ryan Schmidt wrote:
You don't need to install any ports; all ports' portfiles are
already on your computer. Just go to the dports directory and grep
through them. Portfiles are always in a directory for the port,
which is in a directory for the group. So in the d
On Nov 8, 2008, at 20:03, Scott Haneda wrote:
On Nov 8, 2008, at 2:53 PM, Ryan Schmidt wrote:
On Nov 7, 2008, at 20:49, Scott Haneda wrote:
First, there is the issue of needing to do things to the files
while they are freshly unpacked. I am yet to find a good way to
recursively act on a
Scott Haneda wrote:
>> Concerning the dependencies
>> if there are so many, perhaps if you published a list of what's needed
>> others might lend a hand.
>
> Sure, I can find some, but not others:
> Net::DNS
> Compress::Zlib
> Digest::MD5
> Email::MIME::Modifier new
> Email::Valid
> File::ReadBackw
On Nov 8, 2008, at 2:41 PM, David Evans wrote:
Can you post a copy of your Portfile as it currently is? Or did I miss
it?
I am largely using this as a chance to learn portfiles and tcl, so it
is a bit of a testing bed now. I just managed a clean recusrsive
listing function. Was good to d
On Nov 8, 2008, at 2:53 PM, Ryan Schmidt wrote:
On Nov 7, 2008, at 20:49, Scott Haneda wrote:
Is there a long standing debate on this list that a normal reply
does not go back to the list? I am sorry to all of you who I have
replied to direct, I did intend for it to go to the list for the
[Adjusting topic to be a bit more descriptive of the current discussion]
On Nov 8, 2008, at 2:53 PM, Ryan Schmidt wrote:
There is a function fs-traverse in MacPorts designed for this. Grep
through the existing portfiles to see how this can be used.
As one of the authors of that function, I'd
On Nov 7, 2008, at 20:49, Scott Haneda wrote:
Is there a long standing debate on this list that a normal reply
does not go back to the list? I am sorry to all of you who I have
replied to direct, I did intend for it to go to the list for the
benefit of the archives.
Press the Reply All
Scott --
Can you post a copy of your Portfile as it currently is? Or did I miss
it? Concerning the dependencies
if there are so many, perhaps if you published a list of what's needed
others might lend a hand.
It does look like you picked a tough case for your first Portfile.
Dave
_
Any chance someone can take a poke at this one? I'm trying to have a
running port by wekkends end.
I know there is a lot in there but I'm stumped.
Thanks.
--
Scott
Iphone says hello.
On Nov 7, 2008, at 6:49 PM, Scott Haneda <[EMAIL PROTECTED]> wrote:
Is there a long standing debate on this
Is there a long standing debate on this list that a normal reply does
not go back to the list? I am sorry to all of you who I have replied
to direct, I did intend for it to go to the list for the benefit of
the archives.
On Nov 6, 2008, at 1:06 AM, Bryan Blackburn wrote:
What goes in there
On Nov 6, 2008, at 04:12, Scott Haneda wrote:
On Nov 6, 2008, at 1:52 AM, Ryan Schmidt wrote:
On Nov 6, 2008, at 03:45, Scott Haneda wrote:
Is this acceptable in my testing:
puts "+++OTHER DEBUG: worksrcdir: ${worksrcdir}"
Seems to work like print or echo, I could not get the example
On Nov 6, 2008, at 03:52, Ryan Schmidt wrote:
On Nov 6, 2008, at 03:45, Scott Haneda wrote:
In the past, we had this issue where no one knew why they were
removing the spaces from the file name, and I am about to do the
same, as I can not get it to work.
Here is the error message, right w
On Nov 6, 2008, at 03:45, Scott Haneda wrote:
This language is tcl I take it, which I have no experience with.
Yes, it's tcl. I didn't have much experience with it until MacPorts
either. It's not too hard to learn. At its most basic, which suffices
for many portfiles, it reads like a confi
This language is tcl I take it, which I have no experience with.
Is this acceptable in my testing:
puts "+++OTHER DEBUG: worksrcdir: ${worksrcdir}"
Seems to work like print or echo, I could not get the example posted
to this list to work:
*You can "ui_info ${worksrcpath}" or "return -code
On Nov 6, 2008, at 1:01 AM, Ryan Schmidt wrote:
sudo port install assp
Portfile changed since last build; discarding previous state.
---> Fetching assp
---> Verifying checksum(s) for assp
---> Extracting assp
---> Configuring assp
Error: Target org.macports.configure returned: configure fail
On Thu, Nov 06, 2008 at 12:51:44AM -0800, Scott Haneda said:
[...]
> sudo port install assp
> Portfile changed since last build; discarding previous state.
> ---> Fetching assp
> ---> Verifying checksum(s) for assp
> ---> Extracting assp
> ---> Configuring assp
> Error: Target org.macports.conf
On Nov 6, 2008, at 02:51, Scott Haneda wrote:
On Nov 6, 2008, at 12:37 AM, Ryan Schmidt wrote:
I would assume, the Win32::Daemon is not needed, and that many
of these may be available to the perl that ports already has in
place, but I am not sure.
Is it correct that case is a non issue i
On Nov 6, 2008, at 12:37 AM, Ryan Schmidt wrote:
I would assume, the Win32::Daemon is not needed, and that many of
these may be available to the perl that ports already has in
place, but I am not sure.
Is it correct that case is a non issue in something like `port
search net-dns`? I see
On Nov 6, 2008, at 02:30, Scott Haneda wrote:
On Nov 5, 2008, at 11:37 PM, Ryan Schmidt wrote:
On Nov 6, 2008, at 01:34, Scott Haneda wrote:
On Nov 5, 2008, at 9:41 PM, Ryan Schmidt wrote:
Declare dependencies on those ports in the assp port. For
example, if they are library dependencies,
On Nov 5, 2008, at 11:37 PM, Ryan Schmidt wrote:
On Nov 6, 2008, at 01:34, Scott Haneda wrote:
On Nov 5, 2008, at 9:41 PM, Ryan Schmidt wrote:
Declare dependencies on those ports in the assp port. For example,
if they are library dependencies, write:
depends_lib-append port:p5-perl-ldap
Bryan Blackburn wrote:
Can you elaborate a little on this, I am not sure I understand
what you
mean. What would you suggest I do? I already have ASSP running
via hand
compile, but wanted to use this as a way to possibly supply a working
install back to the community. Same with mrtg as wel
On Nov 6, 2008, at 01:34, Scott Haneda wrote:
On Nov 5, 2008, at 9:41 PM, Ryan Schmidt wrote:
Declare dependencies on those ports in the assp port. For example,
if they are library dependencies, write:
depends_lib-append port:p5-perl-ldap
You can discover that the port p5-perl-ldap exists
On Nov 5, 2008, at 8:05 PM, Bryan Blackburn wrote:
On Wed, Nov 05, 2008 at 07:08:17PM -0800, Scott Haneda said:
[...]
This is my first effort to make a port update file locally on my
machine,
so be gentle :)
For a first Portfile, this is a bad choice, it does nearly all steps
manually (co
On Nov 5, 2008, at 9:41 PM, Ryan Schmidt wrote:
Declare dependencies on those ports in the assp port. For example,
if they are library dependencies, write:
depends_lib-append port:p5-perl-ldap
You can discover that the port p5-perl-ldap exists by typing "port
search ldap" and looking throu
On Wed, Nov 05, 2008 at 09:15:40PM -0800, Scott Haneda said:
> Thanks Bryan, see comments below:
>
> On Nov 5, 2008, at 8:05 PM, Bryan Blackburn wrote:
>
>> On Wed, Nov 05, 2008 at 07:08:17PM -0800, Scott Haneda said:
>> [...]
>>>
>>> This is my first effort to make a port update file locally on my
On Nov 5, 2008, at 10:27 PM, Ryan Schmidt wrote:
Hypothetical additional phases before the fetch phase would not
cause problems for the existing strategy. The point of checking and
bailing before the fetch phase is that we don't want someone
downloading a large file if we already know they
On Nov 6, 2008, at 00:23, Jordan K. Hubbard wrote:
On Nov 5, 2008, at 9:59 PM, Ryan Schmidt wrote:
Yes, using pre-fetch to print out fatal error messages has been
the recommendation until this point, and it works fine.
Sure, it works fine, right up until the point where someone invents
a
We'll skip the push-ups this time.
On Nov 6, 2008, at 00:17, Scott Haneda wrote:
Cool, thanks... Just skimmed the relevant parts of the guide. Will
read in detail as I go along. Strange, a little excited to get
started
Thanks for everyone being so helpful, even on IRC, macports just
On Nov 5, 2008, at 9:59 PM, Ryan Schmidt wrote:
Yes, using pre-fetch to print out fatal error messages has been the
recommendation until this point, and it works fine.
Sure, it works fine, right up until the point where someone invents a
"sniff" target stage (for security, of course) and sa
Cool, thanks... Just skimmed the relevant parts of the guide. Will
read in detail as I go along. Strange, a little excited to get
started
Thanks for everyone being so helpful, even on IRC, macports just made
my top 10 list of nice communities :) There are some rough ones out
there f
On Nov 5, 2008, at 23:21, Scott Haneda wrote:
On Nov 5, 2008, at 7:38 PM, Ryan Schmidt wrote:
On Nov 5, 2008, at 21:08, Scott Haneda wrote:
On Nov 5, 2008, at 4:04 PM, David Evans wrote:
Scott Haneda wrote:
This port installs clean, and really nice:
http://trac.macports.org/browser/trunk/dpo
On Nov 5, 2008, at 23:50, Jordan K. Hubbard wrote:
On Nov 5, 2008, at 9:38 PM, Ryan Schmidt wrote:
You can do something like
platform darwin 7 {
pre-fetch {
return -code error "${name} requires Mac OS X 10.4 or later"
}
}
Ooh. People are using pre-fetch as a
On Nov 5, 2008, at 9:38 PM, Ryan Schmidt wrote:
You can do something like
platform darwin 7 {
pre-fetch {
return -code error "${name} requires Mac OS X 10.4 or later"
}
}
Ooh. People are using pre-fetch as an "initializer" for the
Portfile? Ugh. I never
On Nov 5, 2008, at 23:15, Scott Haneda wrote:
On Nov 5, 2008, at 8:05 PM, Bryan Blackburn wrote:
On Wed, Nov 05, 2008 at 07:08:17PM -0800, Scott Haneda said:
[...]
This is my first effort to make a port update file locally on my
machine,
so be gentle :)
For a first Portfile, this is a
On Nov 5, 2008, at 23:33, Scott Haneda wrote:
On Nov 5, 2008, at 8:05 PM, Bryan Blackburn wrote:
On Wed, Nov 05, 2008 at 07:08:17PM -0800, Scott Haneda said:
[...]
This is my first effort to make a port update file locally on my
machine,
so be gentle :)
For a first Portfile, this is a b
On Nov 5, 2008, at 8:05 PM, Bryan Blackburn wrote:
On Wed, Nov 05, 2008 at 07:08:17PM -0800, Scott Haneda said:
[...]
This is my first effort to make a port update file locally on my
machine,
so be gentle :)
For a first Portfile, this is a bad choice, it does nearly all steps
manually (co
Thanks Bryan, see comments below:
On Nov 5, 2008, at 8:05 PM, Bryan Blackburn wrote:
On Wed, Nov 05, 2008 at 07:08:17PM -0800, Scott Haneda said:
[...]
This is my first effort to make a port update file locally on my
machine,
so be gentle :)
For a first Portfile, this is a bad choice, it
On Wed, Nov 05, 2008 at 07:08:17PM -0800, Scott Haneda said:
[...]
>
> This is my first effort to make a port update file locally on my machine,
> so be gentle :)
For a first Portfile, this is a bad choice, it does nearly all steps
manually (configure, no build, and destroot are all there in the
On Nov 5, 2008, at 21:08, Scott Haneda wrote:
On Nov 5, 2008, at 4:04 PM, David Evans wrote:
Scott Haneda wrote:
This port installs clean, and really nice:
http://trac.macports.org/browser/trunk/dports/mail/assp/Portfile
however, I can not locate a maintainer, as it is woefully out of
dat
David, I forgot "reply-all" on this mailing list, so ignore my direct
communication email please, this was meant for the list, thanks.
On Nov 5, 2008, at 4:04 PM, David Evans wrote:
Scott Haneda wrote:
This port installs clean, and really nice:
http://trac.macports.org/browser/trunk/dports/m
Scott Haneda wrote:
> This port installs clean, and really nice:
> http://trac.macports.org/browser/trunk/dports/mail/assp/Portfile
>
> however, I can not locate a maintainer, as it is woefully out of date.
> nameassp
> version 1.1.0
>
> ASSP 1.3.3.10 is current,
This port installs clean, and really nice:
http://trac.macports.org/browser/trunk/dports/mail/assp/Portfile
however, I can not locate a maintainer, as it is woefully out of date.
nameassp
version 1.1.0
ASSP 1.3.3.10 is current, and also, there is a very strong
63 matches
Mail list logo
