On Thu, 06 Dec 2007 06:34:05 -0600, GP <[EMAIL PROTECTED]> wrote:
- Respect the CC, CFLAGS and LOCALBASE. See in post-patch.
- Add kissdx.in in 'files' directory.
- Remove that add_to_conf stuff in Makefile, use pkg-message.
Thank you Mezz, for going through my makefiles and making it confo
On Thu, Dec 06, 2007 at 10:22:06PM +0100, GP wrote:
>>> rc.conf
>>> It's a shame that I can't use a script placed in /files to change rc.conf
>>> during install/
>>> deinstall. I really liked that. But i guess I will settle with a dull
>>> pkg-message at the
>>> end, like the rest of you...
>>>
>>
rc.conf
It's a shame that I can't use a script placed in /files to change rc.conf
during install/
deinstall. I really liked that. But i guess I will settle with a dull
pkg-message at the
end, like the rest of you...
Well, no, it's not a shame. The last thing we want to do as a community
is enab
--On Thursday, December 06, 2007 13:34:05 +0100 GP <[EMAIL PROTECTED]>
wrote:
rc.conf
It's a shame that I can't use a script placed in /files to change rc.conf
during install/
deinstall. I really liked that. But i guess I will settle with a dull
pkg-message at the
end, like the rest of you...
W
- Respect the CC, CFLAGS and LOCALBASE. See in post-patch.
- Add kissdx.in in 'files' directory.
- Remove that add_to_conf stuff in Makefile, use pkg-message.
Thank you Mezz, for going through my makefiles and making it conform to the
principals of
the ports system. That was a very big help
On Tue, 04 Dec 2007 06:36:20 -0600, GP <[EMAIL PROTECTED]> wrote:
$(MKDIR) $(FILESDIR)
$(CP) ${WRKSRC}/kissdx.in ${FILESDIR}
I don't really like to create FILESDIR and move from WRKSRC to
FILESDIR. The WRKDIR/WRKSRC are the place where you work anything
inside. However, move from WRKSRC t
$(MKDIR) $(FILESDIR)
$(CP) ${WRKSRC}/kissdx.in ${FILESDIR}
I don't really like to create FILESDIR and move from WRKSRC to
FILESDIR. The WRKDIR/WRKSRC are the place where you work anything
inside. However, move from WRKSRC to FILESDIR might create problem in
future so avoid that.
When I lev
On Mon, 03 Dec 2007 15:50:21 -0600, GP <[EMAIL PROTECTED]> wrote:
Thanks a lot!
I have as you sugested, but have a problems:
$(MKDIR) $(FILESDIR)
$(CP) ${WRKSRC}/kissdx.in ${FILESDIR}
I don't really like to create FILESDIR and move from WRKSRC to
FILESDIR. The WRKDIR/WRKSRC are the place
Thanks a lot!
I have as you sugested, but have a problems:
$(MKDIR) $(FILESDIR)
$(CP) ${WRKSRC}/kissdx.in ${FILESDIR}
I don't really like to create FILESDIR and move from WRKSRC to FILESDIR.
The WRKDIR/WRKSRC are the place where you work anything inside. However,
move from WRKSRC to FILESD
On Sun, 02 Dec 2007 15:37:57 -0600, GP <[EMAIL PROTECTED]> wrote:
Ok. thanks.
Its simple so I will just put in in this mail.
I hope to have the ability to make changes in the source, so I've
included
the proposed application
Makefile as well.
Its all working, but I would like to know
Many ports need this to work, sadly it is often not mentioned at the
end of make install or the pkg_add. I would love for it to say
something like this. We need to make this easier to use when possible.
In order for the install of "port name" to work, it should be activated
via /etc.rc.conf,
GP wrote:
You should not make changes to /etc/rc.conf at all from a port. Please
remove that before submitting.
Thanks,
Doug
Thanks I will, but how should it be done? I must be there for it to work?
___
freebsd-ports@freebsd.org mailing list
http://
You should not make changes to /etc/rc.conf at all from a port. Please
remove that before submitting.
Thanks,
Doug
Thanks I will, but how should it be done? I must be there for it to work?
___
freebsd-ports@freebsd.org mailing list
http://lists.freeb
GP wrote:
>>> Hi and welcome!
>>> First of all you should install ports-mgmt/portlint and run it against
>>> your port (if you haven't done it already). Be sure to use the switch to
>>> enable additional checks (I got bitten once because I forgot it).
>>> Then you could perhaps put your work onlin
Any body?
I'm new to porting for FreeBSD and make files aren't my strongest suit.
So
I would be greatful if I could get an experienced porter to review my
make
files, for at very simple deamon.
I've read the porter handbook and the port seems to be working fine.
But
I'm uncertain as to what
I'm new to porting for FreeBSD and make files aren't my strongest suit.
So
I would be greatful if I could get an experienced porter to review my
make
files, for at very simple deamon.
I've read the porter handbook and the port seems to be working fine. But
I'm uncertain as to what is best pract
On Sat, 01 Dec 2007 00:38:16 +0100, GP wrote:
>
> - Original Message -
> From: "GP" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, December 01, 2007 12:37 AM
> Subject: HELP needed by experienced porter for simple review
>
&g
- Original Message -
From: "GP" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, December 01, 2007 12:37 AM
Subject: HELP needed by experienced porter for simple review
I'm new to porting for FreeBSD and make files aren't my strongest su
18 matches
Mail list logo