Re: My first port
On Mon, Jun 22, 2020 at 4:42 AM Nikolaj Thygesen wrote: > > On Mon, 22 Jun 2020 06:04:22 +0600 > Muhammad Moinur Rahman wrote: > > > Hi, > > > > Try to find out the reference location "share/pkgconfig” in the CMake > > file. Then you can use REIINPLACE_CMD to change that line or modify > > accordingly. > > > > The purpose of @sample is not this. @sample is primarily used for > > configuration files. > > > > Regards, > > Moin > > > > Hi, > > Thanks for the replies; I did a REINPLACE and it works - just for the > record, I first tried pathfix, but that seems not to work for cmake!? Hrmmn, it should if you also have USES=cmake. That said, if the file you're patching isn't CMakeLists.txt, you'd need to set PATHFIX_CMAKELISTSTXT=YourFileNameHere.txt. I'm glad you got it working though! # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.org ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: My first port
On Mon, 22 Jun 2020 06:04:22 +0600 Muhammad Moinur Rahman wrote: > Hi, > > Try to find out the reference location "share/pkgconfig” in the CMake > file. Then you can use REIINPLACE_CMD to change that line or modify > accordingly. > > The purpose of @sample is not this. @sample is primarily used for > configuration files. > > Regards, > Moin > Hi, Thanks for the replies; I did a REINPLACE and it works - just for the record, I first tried pathfix, but that seems not to work for cmake!? br - N :o) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: My first port
On Mon, 22 Jun 2020 at 03:04, Muhammad Moinur Rahman wrote: > > Hi, > > Try to find out the reference location "share/pkgconfig” in the CMake file. > Then you can use REIINPLACE_CMD to change that line or modify accordingly. 'USES= pathfix' will do this job: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/uses-pathfix.html Max ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: My first port
On Sun, Jun 21, 2020 at 4:11 PM Nikolaj Thygesen
wrote:
>
> Hi freebsd-ports,
>
> I'm trying to create my first port and things are taking shape, but
> I'm down to one little detail making me feel a bit dirty. The port is based
> on the latest release of swi-prolog, which has switched to cmake/ninja. My
> final issue is that the pkg-conf-.pc file gets installed in
> PREFIX/share/pkgconfig instead of PREFIX/libdata/pkgconfig, but I can't find
> the best way to maneuver it into the right directory.
> My current hack-ish solution has been to add to pkg-plist a line like:
>
> @sample share/pkgconfig/swipl.pc libdata/pkgconfig/swipl.pc
>
> ... which actually works, but it feels wrong. Is there a better more standard
> way to do this?
If you can't find and patch the location in the cmake files (like
Muhammad advised), the easiest solution is to move it in post-install.
But Muhammad's solution is the best option and you should shoot for
that first.
post-install:
${MV} ${STAGEDIR}${PREFIX}/share/pkgconfig/swipl.pc
${STAGEDIR}${PREFIX}/libdata/pkgconfig
# Adam
--
Adam Weinberger
ad...@adamw.org
https://www.adamw.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: My first port
Hi, Try to find out the reference location "share/pkgconfig” in the CMake file. Then you can use REIINPLACE_CMD to change that line or modify accordingly. The purpose of @sample is not this. @sample is primarily used for configuration files. Regards, Moin > On 22 Jun, 2020, at 04:11, Nikolaj Thygesen wrote: > > Hi freebsd-ports, > > I'm trying to create my first port and things are taking shape, but I'm > down to one little detail making me feel a bit dirty. The port is based on > the latest release of swi-prolog, which has switched to cmake/ninja. My final > issue is that the pkg-conf-.pc file gets installed in PREFIX/share/pkgconfig > instead of PREFIX/libdata/pkgconfig, but I can't find the best way to > maneuver it into the right directory. > My current hack-ish solution has been to add to pkg-plist a line like: > > @sample share/pkgconfig/swipl.pc libdata/pkgconfig/swipl.pc > > ... which actually works, but it feels wrong. Is there a better more standard > way to do this? > > br - Nikolaj > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" signature.asc Description: Message signed with OpenPGP
My first port
Hi freebsd-ports, I'm trying to create my first port and things are taking shape, but I'm down to one little detail making me feel a bit dirty. The port is based on the latest release of swi-prolog, which has switched to cmake/ninja. My final issue is that the pkg-conf-.pc file gets installed in PREFIX/share/pkgconfig instead of PREFIX/libdata/pkgconfig, but I can't find the best way to maneuver it into the right directory. My current hack-ish solution has been to add to pkg-plist a line like: @sample share/pkgconfig/swipl.pc libdata/pkgconfig/swipl.pc ... which actually works, but it feels wrong. Is there a better more standard way to do this? br - Nikolaj ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
updating my first port
Hi all,
I'm updating a port for the first time. I've made the changes and done all
the tests and it works fine. I'm using the SVN option in the handbook and
I've updated the files and got
root@test:/usr/local/ports_update/taskjuggler # svn status
M Makefile
M distinfo
I'm trying to create a diff as per the last part but I'm not quite sure
what they mean by basename
The last step is to make a unified
diff(1)http://www.freebsd.org/cgi/man.cgi?query=diffsektion=1 of
the files against SVN:
% *svn diff ../`basename ${PWD}`.diff*
Any pointers?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: updating my first port
On Wed, Oct 30, 2013 at 5:56 PM, Alex Laurie alex.r.lau...@gmail.comwrote:
Hi all,
I'm updating a port for the first time. I've made the changes and done all
the tests and it works fine. I'm using the SVN option in the handbook and
I've updated the files and got
root@test:/usr/local/ports_update/taskjuggler # svn status
M Makefile
M distinfo
I'm trying to create a diff as per the last part but I'm not quite sure
what they mean by basename
The last step is to make a unified
diff(1)http://www.freebsd.org/cgi/man.cgi?query=diffsektion=1 of
the files against SVN:
% *svn diff ../`basename ${PWD}`.diff*
${PWD} contains the directory you are working on, for instance
~/my_ports/my_thirdparty_application.
basename ${PWD} strips everything from that path up to (and including) the
slash, this is, it gives you my_thirdparty_application (without the
quotes).
The whole command is just to create a diff of your files against the repo
and calling the diff file with the same name as the directory you are in.
Notice that it adds the .diff to the file name.
HTH
Any pointers?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [SUBMITTED] linux-f10-nss_ldap: my first port - be gentle :)
On 01/14/12 05:53, Boris Samorodov wrote: 13.01.2012 18:51, Da Rock пишет: Once submitted do the committers offer any advice on improvements? Yep, it happens from sometime. Ok. I've submitted; but I have a problem viewing it on the pr web page. According to my mail system it has gone through hours ago. Is the system manual or automatic? One other thing: this process of porting (Makefiles and such) are these standard commands, functions, formatting for make? Or is it solely FreeBSD specific? Aside from policies and such of course... This is the first time I've used Makefiles to any such depth you see, so I'm curious to know where make stuff ends and the Freebsd tweaks begin. I know I have to read the mk files more thoroughly, but not even all the quirks in there would be completely FreeBSD in origin. So I suppose I'm asking how to tell the difference between the two. Cheers ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [SUBMITTED] linux-f10-nss_ldap: my first port - be gentle :)
On 14 January 2012 11:42, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 01/14/12 05:53, Boris Samorodov wrote: 13.01.2012 18:51, Da Rock пишет: Once submitted do the committers offer any advice on improvements? Yep, it happens from sometime. Ok. I've submitted; but I have a problem viewing it on the pr web page. According to my mail system it has gone through hours ago. Is the system manual or automatic? One other thing: this process of porting (Makefiles and such) are these standard commands, functions, formatting for make? Or is it solely FreeBSD specific? Aside from policies and such of course... This is the first time I've used Makefiles to any such depth you see, so I'm curious to know where make stuff ends and the Freebsd tweaks begin. I know I have to read the mk files more thoroughly, but not even all the quirks in there would be completely FreeBSD in origin. So I suppose I'm asking how to tell the difference between the two. We do have our own make (pmake), which is about as different as you can get from gmake (GNU make). You're better off finding a tutorial on how to write a Makefile; the way ports ones are written doesn't give a good understanding on how they normally work. Chris Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/12/12 17:54, Matthew Seaman wrote: On 12/01/2012 06:44, Da Rock wrote: I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also have the files hosted and the MASTER_FILES set to include the linux sites (just where the files are located). I am looking for a backup site to all that IF I can twist someones arm? I have triple tested it all in all iterations and its as smooth as now- no issues whatsoever. So what happens now? How does it get into the ports tree now? Can someone have a look see and test it before I submit this thing? Run 'portlint -C' and fix anything it flags up -- well, within reason. Sometimes portlint complains about things it shouldn't. Then submit your port. For a new port, you need to create a .shar of the port directory, which you can attach to the PR like so: send-pr -a newport.shar When filling in the PR in the editor it pops you into, you need to set the appropriate field in the PR to 'change-request'. No need to fill in all the sections -- for ports PRs it's mostly 'Description' that gets filled in. Everything else is pretty obvious I think. The comitter who works on the port will run it through tinderbox testing and get back to you if there are any problems. I would have preferred to know about the -C option earlier- I hadn't realised how helpful it was. I used -Cv in the end which gave me a better overview. I do have a WARN: no CVS directories. Use -N to check a new port. Is this normal? Is this simply expected of a new uncommitted port? I assume this is the case due to -N mentioned in the warning, I also ran it with -CvN and it came back with looks fine. I'll upload a new .shar to my URI now. THX :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 12 January 2012 12:26, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 01/12/12 17:54, Matthew Seaman wrote: On 12/01/2012 06:44, Da Rock wrote: I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also have the files hosted and the MASTER_FILES set to include the linux sites (just where the files are located). I am looking for a backup site to all that IF I can twist someones arm? I have triple tested it all in all iterations and its as smooth as now- no issues whatsoever. So what happens now? How does it get into the ports tree now? Can someone have a look see and test it before I submit this thing? Run 'portlint -C' and fix anything it flags up -- well, within reason. Sometimes portlint complains about things it shouldn't. Then submit your port. For a new port, you need to create a .shar of the port directory, which you can attach to the PR like so: send-pr -a newport.shar When filling in the PR in the editor it pops you into, you need to set the appropriate field in the PR to 'change-request'. No need to fill in all the sections -- for ports PRs it's mostly 'Description' that gets filled in. Everything else is pretty obvious I think. The comitter who works on the port will run it through tinderbox testing and get back to you if there are any problems. I would have preferred to know about the -C option earlier- I hadn't realised how helpful it was. I used -Cv in the end which gave me a better overview. I do have a WARN: no CVS directories. Use -N to check a new port. Is this normal? Is this simply expected of a new uncommitted port? I assume this is the case due to -N mentioned in the warning, I also ran it with -CvN and it came back with looks fine. I'll upload a new .shar to my URI now. Hm, for a new port, you should use portlint -A; portlint -C is for existing ports. portlint -A searches for stupid things like a work/ directory still existing too. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/13/12 04:19, Chris Rees wrote: On 12 January 2012 12:26, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 01/12/12 17:54, Matthew Seaman wrote: On 12/01/2012 06:44, Da Rock wrote: I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also have the files hosted and the MASTER_FILES set to include the linux sites (just where the files are located). I am looking for a backup site to all that IF I can twist someones arm? I have triple tested it all in all iterations and its as smooth as now- no issues whatsoever. So what happens now? How does it get into the ports tree now? Can someone have a look see and test it before I submit this thing? Run 'portlint -C' and fix anything it flags up -- well, within reason. Sometimes portlint complains about things it shouldn't. Then submit your port. For a new port, you need to create a .shar of the port directory, which you can attach to the PR like so: send-pr -a newport.shar When filling in the PR in the editor it pops you into, you need to set the appropriate field in the PR to 'change-request'. No need to fill in all the sections -- for ports PRs it's mostly 'Description' that gets filled in. Everything else is pretty obvious I think. The comitter who works on the port will run it through tinderbox testing and get back to you if there are any problems. I would have preferred to know about the -C option earlier- I hadn't realised how helpful it was. I used -Cv in the end which gave me a better overview. I do have a WARN: no CVS directories. Use -N to check a new port. Is this normal? Is this simply expected of a new uncommitted port? I assume this is the case due to -N mentioned in the warning, I also ran it with -CvN and it came back with looks fine. I'll upload a new .shar to my URI now. Hm, for a new port, you should use portlint -A; portlint -C is for existing ports. portlint -A searches for stupid things like a work/ directory still existing too. portlint -A: looks fine. I'll put it in later today, I think. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
--On January 11, 2012 10:44:11 AM +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
My last problem is with the define knobs. I have an .if defined(WITH_PAM)
.else ... .endif statement, but it keeps giving me trouble. I can't quite
figure what I've got wrong. The statement looks like this:
post-extract:
.if defined(WITH_PAM)
PLIST_FILES+=lib/security/pam_ldap.so
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so
${DIRRM} ${WRKDIR}/lib/;
fi
^
This is what's wrong. In port Makefiles, it's .if, .else, .endif not fi.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, Jan 11, 2012 at 10:37 AM, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
--On January 11, 2012 10:44:11 AM +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
My last problem is with the define knobs. I have an .if defined(WITH_PAM)
.else ... .endif statement, but it keeps giving me trouble. I can't quite
figure what I've got wrong. The statement looks like this:
post-extract:
.if defined(WITH_PAM)
PLIST_FILES+=lib/security/pam_ldap.so
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so
${DIRRM} ${WRKDIR}/lib/;
fi
^
This is what's wrong. In port Makefiles, it's .if, .else, .endif not fi.
You need both: .endif and fi in this case (the 'fi' is part of the shell script)
--
Eitan Adler
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/11/12 11:10 AM, Eitan Adler wrote:
On Wed, Jan 11, 2012 at 10:37 AM, Paul Schmehl pschmehl_li...@tx.rr.com
wrote:
--On January 11, 2012 10:44:11 AM +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
My last problem is with the define knobs. I have an .if defined(WITH_PAM)
.else ... .endif statement, but it keeps giving me trouble. I can't quite
figure what I've got wrong. The statement looks like this:
post-extract:
.if defined(WITH_PAM)
PLIST_FILES+=lib/security/pam_ldap.so
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so
${DIRRM} ${WRKDIR}/lib/;
fi
^
This is what's wrong. In port Makefiles, it's .if, .else, .endif not fi.
You need both: .endif and fi in this case (the 'fi' is part of the shell
script)
You'll also need to insert line continuations and command delimiters in
the shell script portion, in addition to Eitan's change.
Cheers,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/ - Follow you, follow me
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8NtigACgkQ0sRouByUApBnQwCfZGapwauaK4QtNGOwDd3V3mZZ
YiwAn2iIERynVsf2nNlkZpZniF5snJCf
=6aKi
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 11/01/2012 16:10, Eitan Adler wrote:
post-extract:
.if defined(WITH_PAM)
PLIST_FILES+=lib/security/pam_ldap.so
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so
${DIRRM} ${WRKDIR}/lib/;
fi
^
This is what's wrong. In port Makefiles, it's .if, .else, .endif not fi.
You need both: .endif and fi in this case (the 'fi' is part of the shell
script)
Also the shell script part needs to be backslashed, and statements
separated by semi-colons, like so:
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so ; \
${DIRRM} ${WRKDIR}/lib/ ; \
fi
Looking back at the OP's previous posts, it's this backslashing thing
which is missing: the (make) .if is properly closed with a .endif, which
unfortunately got cropped in one of the replies upthread.
Another point: its not usual to modify variables like PLIST_FILES or
PORTDOCS as part of the post-extract target. Usually that's done
earlier in the Makefile before any of the actual make targets.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/12/12 02:23, Matthew Seaman wrote:
On 11/01/2012 16:10, Eitan Adler wrote:
post-extract:
.if defined(WITH_PAM)
PLIST_FILES+=lib/security/pam_ldap.so
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so
${DIRRM} ${WRKDIR}/lib/;
fi
^
This is what's wrong. In port Makefiles, it's .if, .else, .endif not fi.
You need both: .endif and fi in this case (the 'fi' is part of the shell script)
Also the shell script part needs to be backslashed, and statements
separated by semi-colons, like so:
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so ; \
${DIRRM} ${WRKDIR}/lib/ ; \
fi
Looking back at the OP's previous posts, it's this backslashing thing
which is missing: the (make) .if is properly closed with a .endif, which
unfortunately got cropped in one of the replies upthread.
Another point: its not usual to modify variables like PLIST_FILES or
PORTDOCS as part of the post-extract target. Usually that's done
earlier in the Makefile before any of the actual make targets.
You were right Matthew.
It's all done now guys- what now?
I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also
have the files hosted and the MASTER_FILES set to include the linux
sites (just where the files are located). I am looking for a backup site
to all that IF I can twist someones arm?
I have triple tested it all in all iterations and its as smooth as now-
no issues whatsoever. So what happens now? How does it get into the
ports tree now? Can someone have a look see and test it before I submit
this thing?
As for the bsd.sites question: before I posted this I navigated to the
sites in question, and they had messages to redirect to this URI that I
have posted.
As for my own files, I can use release, updates, or testing. ATM its set
to the testing files. Should I back that off a bit?
I set the portversion to the nss_ldap_version (264). What about the 6 do
you think? It could be trickier...
The Makefile has lost weight - I trimmed it aggressively, but if I can
cut it back further I'd be happy to know.
I've posted the shar to
http://herveybayaustralia.com.au/ports/distfiles/linux-f10-nss_ldap.shar
if people want to check it out. Please don't hold back if there is
something I've missed.
I have a query on the tabbing - I have either ee or gedit (atm) how can
I set them to the correct tab spacing?
Cheers
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 12/01/2012 06:44, Da Rock wrote: I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also have the files hosted and the MASTER_FILES set to include the linux sites (just where the files are located). I am looking for a backup site to all that IF I can twist someones arm? I have triple tested it all in all iterations and its as smooth as now- no issues whatsoever. So what happens now? How does it get into the ports tree now? Can someone have a look see and test it before I submit this thing? Run 'portlint -C' and fix anything it flags up -- well, within reason. Sometimes portlint complains about things it shouldn't. Then submit your port. For a new port, you need to create a .shar of the port directory, which you can attach to the PR like so: send-pr -a newport.shar When filling in the PR in the editor it pops you into, you need to set the appropriate field in the PR to 'change-request'. No need to fill in all the sections -- for ports PRs it's mostly 'Description' that gets filled in. Everything else is pretty obvious I think. The comitter who works on the port will run it through tinderbox testing and get back to you if there are any problems. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: define issue - linux-f10-nss_ldap: my first port - be gentle :)
--On January 10, 2012 10:52:32 AM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I'm having some trouble using knobs and defined in the Makefile. It keeps complaining about the unexpected. I've tried .if defined(WITH_PAM) and .ifdefined(WITH_PAM) and it complains about an unexpected ( in the first, and an unexpected word in the second. How do I conditionally handle the knobs? You need an if - endif for each knob. Something like this. .if defined(WITH_PAM) CONFIGURE_ARGS+=--with-pam PLIST_SUB+= PAM= .else CONFIGURE_ARGS+=--without-pam PLIST_SUB+= PAM=@comment not installed: .endif ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Mon, 09 Jan 2012 15:55:48 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
The PORTVERSION looks a little bit off to me. I would use something
like ${NSS_LDAP_VERSION} or ${NSS_LDAP_VERSION}.${RPMVERSION} (the
later may look a little bit strange... or not) to make it easy to
compare what is installed on a system with what is available on linux.
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/
\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/
\
http://herveybayaustralia.com.au/ports/distfiles/
I can't remember if we have the fedora archives in bsd.sites.mk (if
not, it would be worth to add it), and I'm too lazy ATM to search for
it. If we have them (and they are OK), it would be better to use the
bsd.sites.mk shortcodes for them. This would change automatically the
master sites for this port if they are changed/improved in bsd.sites.mk.
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
Hmmm... I would expect that USE_LINUX_RPM automatically sets
USE_LINUX_PREFIX... to be verified.
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ];
then \ rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf
${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam* fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
\ usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
\ usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.include bsd.port.mk
The man pages under the linux chroot, but the docs I thought would go
into the /usr/share/doc/as linux-f10-nss_ldap?
If you are talking about the FreeBSD location /usr/share/doc and not
the linux location /compat/linux/usr/share/doc:
Linux ports are special to this. In the linux base we do not bend the
install to put some stuff outside of /compat/linux.
If you talk about the linux location: we do not bend the stuff
inside /compat/linux to complay to the FreeBSD hier-man-page.
Or short: let the RPM install the files where it wants to have them. Do
not move them around.
On an aside I noticed that there is a better site to use straight up
for linux dist rpms- see the MASTER_SITES list in the Makefile. Might
be a good idea to update the list under MASTER_SITE_FEDORA_LINUX to
include these first? The others seem rather empty.
My comment above for bsd.sites.mk was something like you suggest here,
just that it should be MASTER_SITE_FEDORA_LINUX_ARCHIVE or similar (I
hope that the MASTER_SITE_FEDORA_LINUX could be useful as it is for an
hypothetic (= nobody works on something like this ATM) update of the
default linux_base port).
Bye,
Alexander.
--
http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
--On January 10, 2012 10:11:15 PM +0100 Alexander Leidinger
alexan...@leidinger.net wrote:
On Mon, 09 Jan 2012 15:55:48 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
The PORTVERSION looks a little bit off to me. I would use something
like ${NSS_LDAP_VERSION} or ${NSS_LDAP_VERSION}.${RPMVERSION} (the
later may look a little bit strange... or not) to make it easy to
compare what is installed on a system with what is available on linux.
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/update
s/testing/10/i386/ \
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/E
verything/i386/os/Packages/ \
http://herveybayaustralia.com.au/ports/distfiles/
I can't remember if we have the fedora archives in bsd.sites.mk (if
not, it would be worth to add it), and I'm too lazy ATM to search for
it. If we have them (and they are OK), it would be better to use the
bsd.sites.mk shortcodes for them. This would change automatically the
master sites for this port if they are changed/improved in bsd.sites.mk.
Too lazy to do this?
# grep FEDORA /usr/ports/Mk/bsd.*
/usr/ports/Mk/bsd.linux-rpm.mk:MASTER_SITES=
${MASTER_SITE_FEDORA_LINUX}
/usr/ports/Mk/bsd.sites.mk:.if !defined(IGNORE_MASTER_SITE_FEDORA_LINUX)
/usr/ports/Mk/bsd.sites.mk:MASTER_SITE_FEDORA_LINUX+= \
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
Hmmm... I would expect that USE_LINUX_RPM automatically sets
USE_LINUX_PREFIX... to be verified.
USE_LINUX_RPM implies the inclusion of bsd.linux-rpm.mk. bsd.linux-rpm.mk
includes USE_LINUX= yes and USE_LINUX_PREFIX= yes. So putting
USE_LINUX_PREFIX in the Makefile is redundant.
--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/11/12 07:11, Alexander Leidinger wrote:
On Mon, 09 Jan 2012 15:55:48 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
The PORTVERSION looks a little bit off to me. I would use something
like ${NSS_LDAP_VERSION} or ${NSS_LDAP_VERSION}.${RPMVERSION} (the
later may look a little bit strange... or not) to make it easy to
compare what is installed on a system with what is available on linux.
Yeah, I'm still stuck on that - trying to find more info on what to use
there. I've checked the handbook cover to cover, but still haven't
discovered anything. I've left it till last to work out.
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/
\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/
\
http://herveybayaustralia.com.au/ports/distfiles/
I can't remember if we have the fedora archives in bsd.sites.mk (if
not, it would be worth to add it), and I'm too lazy ATM to search for
it. If we have them (and they are OK), it would be better to use the
bsd.sites.mk shortcodes for them. This would change automatically the
master sites for this port if they are changed/improved in bsd.sites.mk.
I'm not 100% sure about the fedora archives, but I don't think they're
exactly right. I keep getting (in most linux ports) a hunt through the
MASTER_SITES for the file, starting with the archives.
The other pbone.net is definitely not in the sites list. I did check
that file thoroughly using grep and by manual sighting.
One thing to note though is that when I tried with MASTER_SITES set to
the FEDORA_LINUX set it failed to find the files. Also the files I need
are only on pbone.net- they are more recent than the original. Or can I
set the rpm version to float a bit?
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
Hmmm... I would expect that USE_LINUX_RPM automatically sets
USE_LINUX_PREFIX... to be verified.
Possibly. I just wanted to be sure. I'll try it with it removed once I
get it working correctly.
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ];
then \ rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf
${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam* fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
\ usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
\ usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.includebsd.port.mk
The man pages under the linux chroot, but the docs I thought would go
into the /usr/share/doc/as linux-f10-nss_ldap?
If you are talking about the FreeBSD location /usr/share/doc and not
the linux location /compat/linux/usr/share/doc:
Linux ports are special to this. In the linux base we do not bend the
install to put some stuff outside of /compat/linux.
If you talk about the linux location: we do not bend the stuff
inside /compat/linux to complay to the FreeBSD hier-man-page.
Or short: let the RPM install the files where it wants to have them. Do
not move them around.
Ok, ok, I'll leave them alone :) I did mention that I was over-thinking
things before... I am pedantic enough to stick by the rules though.
On an aside I noticed that there is a better site to use straight up
for linux dist rpms-
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/11/12 07:11, Alexander Leidinger wrote:
On Mon, 09 Jan 2012 15:55:48 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
The PORTVERSION looks a little bit off to me. I would use something
like ${NSS_LDAP_VERSION} or ${NSS_LDAP_VERSION}.${RPMVERSION} (the
later may look a little bit strange... or not) to make it easy to
compare what is installed on a system with what is available on linux.
Yeah, I'm still stuck on that - trying to find more info on what to use
there. I've checked the handbook cover to cover, but still haven't
discovered anything. I've left it till last to work out.
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/
\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/
\
http://herveybayaustralia.com.au/ports/distfiles/
I can't remember if we have the fedora archives in bsd.sites.mk (if
not, it would be worth to add it), and I'm too lazy ATM to search for
it. If we have them (and they are OK), it would be better to use the
bsd.sites.mk shortcodes for them. This would change automatically the
master sites for this port if they are changed/improved in bsd.sites.mk.
I'm not 100% sure about the fedora archives, but I don't think they're
exactly right. I keep getting (in most linux ports) a hunt through the
MASTER_SITES for the file, starting with the archives.
The other pbone.net is definitely not in the sites list. I did check
that file thoroughly using grep and by manual sighting.
One thing to note though is that when I tried with MASTER_SITES set to
the FEDORA_LINUX set it failed to find the files. Also the files I need
are only on pbone.net- they are more recent than the original. Or can I
set the rpm version to float a bit?
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
Hmmm... I would expect that USE_LINUX_RPM automatically sets
USE_LINUX_PREFIX... to be verified.
Possibly. I just wanted to be sure. I'll try it with it removed once I
get it working correctly.
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ];
then \ rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf
${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam* fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
\ usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
\ usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.includebsd.port.mk
The man pages under the linux chroot, but the docs I thought would go
into the /usr/share/doc/as linux-f10-nss_ldap?
If you are talking about the FreeBSD location /usr/share/doc and not
the linux location /compat/linux/usr/share/doc:
Linux ports are special to this. In the linux base we do not bend the
install to put some stuff outside of /compat/linux.
If you talk about the linux location: we do not bend the stuff
inside /compat/linux to complay to the FreeBSD hier-man-page.
Or short: let the RPM install the files where it wants to have them. Do
not move them around.
Ok, ok, I'll leave them alone :) I did mention that I was over-thinking
things before... I am pedantic enough to stick by the rules though.
On an aside I noticed that there is a better site to use straight up
for linux dist rpms-
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Tue, 10 Jan 2012 15:30:53 -0600 Paul Schmehl
pschmehl_li...@tx.rr.com wrote:
--On January 10, 2012 10:11:15 PM +0100 Alexander Leidinger
alexan...@leidinger.net wrote:
I can't remember if we have the fedora archives in bsd.sites.mk (if
not, it would be worth to add it), and I'm too lazy ATM to search
for it. If we have them (and they are OK), it would be better to
use the bsd.sites.mk shortcodes for them. This would change
automatically the master sites for this port if they are
changed/improved in bsd.sites.mk.
Too lazy to do this?
# grep FEDORA /usr/ports/Mk/bsd.*
/usr/ports/Mk/bsd.linux-rpm.mk:MASTER_SITES=
${MASTER_SITE_FEDORA_LINUX} /usr/ports/Mk/bsd.sites.mk:.if
!defined(IGNORE_MASTER_SITE_FEDORA_LINUX)
/usr/ports/Mk/bsd.sites.mk:MASTER_SITE_FEDORA_LINUX+= \
After a working day debugging an obscure performance issue, I was too
lazy to login into a FreeBSD machine and to do something like the
following in a linux-port directory:
---snip---
% for i in $(make -V MASTER_SITE_FEDORA_LINUX ); do; echo $i ; done |
grep archives
http://archives.fedoraproject.org/pub/archive/fedora/linux/core/%SUBDIR%/
---snip---
So we have the fedora archives inside, but the path is different. This
means either the MASTER_SITE stays at it is, or it can be changed to
include MASTER_SITE_FEDORA_LINUX with a suitable setting for SUBDIR
(SUBDIR=../releases/10/Everything/i386/os/Packages/). Setting SUBDIR
means that all listed master sites need to have the distfile in the
same location. As the pbone-one has a different path than the fedora
archive one, this is either not possible, or one of them should be
changed to point to the same subdir (in this case it only depends upon
Da Rock's own mirror).
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
Hmmm... I would expect that USE_LINUX_RPM automatically sets
USE_LINUX_PREFIX... to be verified.
USE_LINUX_RPM implies the inclusion of bsd.linux-rpm.mk.
bsd.linux-rpm.mk includes USE_LINUX= yes and USE_LINUX_PREFIX= yes.
So putting USE_LINUX_PREFIX in the Makefile is redundant.
Thanks for verifying.
Bye,
Alexander.
--
http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, 11 Jan 2012 10:45:13 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
On 01/11/12 07:11, Alexander Leidinger wrote:
On Mon, 09 Jan 2012 15:55:48 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/
\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/
\
http://herveybayaustralia.com.au/ports/distfiles/
I can't remember if we have the fedora archives in bsd.sites.mk (if
not, it would be worth to add it), and I'm too lazy ATM to search
for it. If we have them (and they are OK), it would be better to
use the bsd.sites.mk shortcodes for them. This would change
automatically the master sites for this port if they are
changed/improved in bsd.sites.mk.
I'm not 100% sure about the fedora archives, but I don't think
they're exactly right. I keep getting (in most linux ports) a hunt
through the MASTER_SITES for the file, starting with the archives.
The other pbone.net is definitely not in the sites list. I did check
that file thoroughly using grep and by manual sighting.
If it is an official mirror, we should maybe add it to bsd.sites.mk.
One thing to note though is that when I tried with MASTER_SITES set
to the FEDORA_LINUX set it failed to find the files. Also the files I
need are only on pbone.net- they are more recent than the original.
Or can I set the rpm version to float a bit?
If they are only available on pbone, there's no need to include the
archives.
Keep the rpm version stable. It's the right thing to do, and making it
dynamic looks a little bit hard as a first port IMO.
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
The .if (and .else / .endif) needs to start at the first character of
the line. As soon as you indent it, it will be executed as a shell
command.
Only one more thing: do I need USE_LDCONFIG?
Yes, for usr/lib/libnss_* it is needed.
Bye,
Alexander.
--
http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 9 Jan 2012 06:01, Da Rock freebsd-po...@herveybayaustralia.com.au
wrote:
All arguments aside, I've finally made headway - I think... its really
frustrating for me because to me it seems a bit of a blackbox atm. I'm
still trying to untangle the threads.
I fiddled and tweaked and finally got make to run. I then ran make
-DPACKAGE_BUILD makesum and got a checksum (SHA256 too). All the while I
had portlint run every now and again spitting out errors I couldn't quite
translate. After makesum I ran it again and it said looks fine. - I
called have slapped it silly! :) Bloody pretentious snot... could've been
more helpful earlier
I just need to work out how to check the checksum against a linux source.
I haven't found that yet.
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/\
http://herveybayaustralia.com.au/ports/distfiles/
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf ${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam*
fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap \
usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.include bsd.port.mk
I'm cutting it to the bone as much as I can. But I am also trying to cut
some of the files that are unnecessary and could be risky. After running
make the directory looks like this:
./
./Makefile
./pkg-descr
./work
./work/etc
./work/etc/ldap.conf
./work/lib
./work/lib/security
./work/lib/security/pam_ldap.so
./work/usr
./work/usr/lib
./work/usr/lib/libnss_ldap-264.so
./work/usr/lib/libnss_ldap.so
./work/usr/lib/libnss_ldap.so.2
./work/usr/share
./work/usr/share/doc
./work/usr/share/doc/nss_ldap-264
./work/usr/share/doc/nss_ldap-264/ANNOUNCE.nss_ldap
./work/usr/share/doc/nss_ldap-264/AUTHORS.nss_ldap
./work/usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.nss_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.pam_ldap
./work/usr/share/doc/nss_ldap-264/ChangeLog.nss_ldap
./work/usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
./work/usr/share/doc/nss_ldap-264/NEWS.nss_ldap
./work/usr/share/doc/nss_ldap-264/NEWS.pam_ldap
./work/usr/share/doc/nss_ldap-264/README.TLS
./work/usr/share/doc/nss_ldap-264/README.nss_ldap
./work/usr/share/doc/nss_ldap-264/README.pam_ldap
./work/usr/share/doc/nss_ldap-264/ldap.conf.nss_ldap
./work/usr/share/doc/nss_ldap-264/ldap.conf.pam_ldap
./work/usr/share/doc/nss_ldap-264/ldapns.schema
./work/usr/share/doc/nss_ldap-264/ns-pwd-policy.schema
./work/usr/share/doc/nss_ldap-264/nsswitch.ldap
./work/usr/share/doc/nss_ldap-264/pam.d
./work/usr/share/doc/nss_ldap-264/pam.d/chfn
./work/usr/share/doc/nss_ldap-264/pam.d/chsh
./work/usr/share/doc/nss_ldap-264/pam.d/ftp
./work/usr/share/doc/nss_ldap-264/pam.d/gdm
./work/usr/share/doc/nss_ldap-264/pam.d/halt
Re: linux-f10-nss_ldap: my first port - be gentle :)
--On January 9, 2012 3:55:48 PM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I just need to work out how to check the checksum against a linux source. I haven't found that yet. My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 09/01/2012 22:28, Paul Schmehl wrote: --On January 9, 2012 3:55:48 PM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I just need to work out how to check the checksum against a linux source. I haven't found that yet. My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? rpms are usually digitally signed. Short of grabbing an appropriate flavour of linux and running yum or whatever on it I wouldn't know how to go about checking that signature though. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Jan 9, 2012, at 2:28 PM, Paul Schmehl wrote: My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? rpm -Va (or rpm --verify --all) ought to consult an MD5 checksum to identify changes for all installed packages... Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/10/12 08:28, Paul Schmehl wrote: --On January 9, 2012 3:55:48 PM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I just need to work out how to check the checksum against a linux source. I haven't found that yet. My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? I don't know. I believe they have a gpg key they use, at least with their repo system. How that specifically works I don't know. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: define issue - linux-f10-nss_ldap: my first port - be gentle :)
I'm having some trouble using knobs and defined in the Makefile. It keeps complaining about the unexpected. I've tried .if defined(WITH_PAM) and .ifdefined(WITH_PAM) and it complains about an unexpected ( in the first, and an unexpected word in the second. How do I conditionally handle the knobs? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Sat, 7 Jan 2012 20:31:04 + Chris Rees cr...@freebsd.org wrote: On 6 January 2012 21:16, Alexander Leidinger alexan...@leidinger.net wrote: The linux ports are a little bit special. They are binary ports and the GPL requires that we distribute the source too. Really? That's not how I read the GPL, nor its interpretation: http://www.gnu.org/licenses/gpl-faq.html#WhatDoesWrittenOfferValid Let's rephrase it: In a discussion with portmgr@, we decided to add the SRPMs to the linux ports, and write code to let the port build cluster fetch the SRPMs too. A normal build without PACKAGE_BUILDING defined should not fetch the SRPMS. This way we make sure the distfiles for the linux binaries are available on FreeBSD-project storage. I do not know if the SPRMs are on the release media or not, but they should be available somewhere on FreeBSD resources. Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
All arguments aside, I've finally made headway - I think... its really
frustrating for me because to me it seems a bit of a blackbox atm. I'm
still trying to untangle the threads.
I fiddled and tweaked and finally got make to run. I then ran make
-DPACKAGE_BUILD makesum and got a checksum (SHA256 too). All the while I
had portlint run every now and again spitting out errors I couldn't
quite translate. After makesum I ran it again and it said looks fine.
- I called have slapped it silly! :) Bloody pretentious snot... could've
been more helpful earlier
I just need to work out how to check the checksum against a linux
source. I haven't found that yet.
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/
\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/
\
http://herveybayaustralia.com.au/ports/distfiles/
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf ${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam*
fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap \
usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.include bsd.port.mk
I'm cutting it to the bone as much as I can. But I am also trying to cut
some of the files that are unnecessary and could be risky. After running
make the directory looks like this:
./
./Makefile
./pkg-descr
./work
./work/etc
./work/etc/ldap.conf
./work/lib
./work/lib/security
./work/lib/security/pam_ldap.so
./work/usr
./work/usr/lib
./work/usr/lib/libnss_ldap-264.so
./work/usr/lib/libnss_ldap.so
./work/usr/lib/libnss_ldap.so.2
./work/usr/share
./work/usr/share/doc
./work/usr/share/doc/nss_ldap-264
./work/usr/share/doc/nss_ldap-264/ANNOUNCE.nss_ldap
./work/usr/share/doc/nss_ldap-264/AUTHORS.nss_ldap
./work/usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.nss_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.pam_ldap
./work/usr/share/doc/nss_ldap-264/ChangeLog.nss_ldap
./work/usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
./work/usr/share/doc/nss_ldap-264/NEWS.nss_ldap
./work/usr/share/doc/nss_ldap-264/NEWS.pam_ldap
./work/usr/share/doc/nss_ldap-264/README.TLS
./work/usr/share/doc/nss_ldap-264/README.nss_ldap
./work/usr/share/doc/nss_ldap-264/README.pam_ldap
./work/usr/share/doc/nss_ldap-264/ldap.conf.nss_ldap
./work/usr/share/doc/nss_ldap-264/ldap.conf.pam_ldap
./work/usr/share/doc/nss_ldap-264/ldapns.schema
./work/usr/share/doc/nss_ldap-264/ns-pwd-policy.schema
./work/usr/share/doc/nss_ldap-264/nsswitch.ldap
./work/usr/share/doc/nss_ldap-264/pam.d
./work/usr/share/doc/nss_ldap-264/pam.d/chfn
./work/usr/share/doc/nss_ldap-264/pam.d/chsh
./work/usr/share/doc/nss_ldap-264/pam.d/ftp
./work/usr/share/doc/nss_ldap-264/pam.d/gdm
./work/usr/share/doc/nss_ldap-264/pam.d/halt
./work/usr/share/doc/nss_ldap-264/pam.d/imap
./work/usr/share/doc/nss_ldap-264/pam.d/kde
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Sat, 07 Jan 2012 12:46:54 +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: And finally checksums: I create a checksum for the port, the linux sites have checksums, and I was advised in passing to check the checksums match. The checksums are going to differ aren't they? Linux and BSD checksums wouldn't be the same, surely? MD5 checksums should always match - it's the same algorithm. Not sure what the various distros use for Linux. -- Gary Jennejohn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/07/12 19:11, Gary Jennejohn wrote: On Sat, 07 Jan 2012 12:46:54 +1000 Da Rockfreebsd-po...@herveybayaustralia.com.au wrote: And finally checksums: I create a checksum for the port, the linux sites have checksums, and I was advised in passing to check the checksums match. The checksums are going to differ aren't they? Linux and BSD checksums wouldn't be the same, surely? MD5 checksums should always match - it's the same algorithm. Not sure what the various distros use for Linux. Thats my point - linux uses SHA256 I believe. And thats not my biggest problem. As I suspected the linux sites have removed the rpm, so I have to either find it on a host somewhere or host it myself. My goal is to somehow prepend MASTERSITES to look to my host first, then one of the linux sites, then a backup host? and hopefully one will hit if mine is down for whatever reason. Has anyone had any experience with rpm.pbone.net? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 07.01.2012 14:01 (UTC+1), Da Rock wrote: On 01/07/12 19:11, Gary Jennejohn wrote: On Sat, 07 Jan 2012 12:46:54 +1000 Da Rockfreebsd-po...@herveybayaustralia.com.au wrote: And finally checksums: I create a checksum for the port, the linux sites have checksums, and I was advised in passing to check the checksums match. The checksums are going to differ aren't they? Linux and BSD checksums wouldn't be the same, surely? MD5 checksums should always match - it's the same algorithm. Not sure what the various distros use for Linux. Thats my point - linux uses SHA256 I believe. If I am not totally wrong here, FreeBSD has changed its ports checksums towards SHA256 for a while now. See for example #head emulators/linux_base-f10/distinfo.i386 SHA256 (rpm/i386/fedora/10/basesystem-10.0-1.noarch.rpm) = 16ad30fc4e4efbb61c62dc2c6ec55d66273a51579421b3a7e12114f9e5313b05 SIZE (rpm/i386/fedora/10/basesystem-10.0-1.noarch.rpm) = 2915 SHA256 (rpm/i386/fedora/10/bash-3.2-30.fc10.i386.rpm) = 83e29d12db4274568b612d61945669cf520222b20ca4dcfba995ccdda48d3afb SIZE (rpm/i386/fedora/10/bash-3.2-30.fc10.i386.rpm) = 1887256 SHA256 (rpm/i386/fedora/10/bzip2-1.0.5-3.fc10.i386.rpm) = 2b70c36689f5bff15309c360f479f67bdcb5defcb1bbd7d24505bbb53b7a5360 SIZE (rpm/i386/fedora/10/bzip2-1.0.5-3.fc10.i386.rpm) = 50129 SHA256 (rpm/i386/fedora/10/bzip2-libs-1.0.5-3.fc10.i386.rpm) = 6c2ff130e5114c5d7cf5e0d5a30c7cd10c92e2602c1a4c12bc94f3f53ab47998 SIZE (rpm/i386/fedora/10/bzip2-libs-1.0.5-3.fc10.i386.rpm) = 39174 SHA256 (rpm/i386/fedora/10/compat-db-4.6.21-5.fc10.i386.rpm) = bead077a94f027f3cc1c115c9ea8602f5807c1e23242b355befdbb1149ad2168 SIZE (rpm/i386/fedora/10/compat-db-4.6.21-5.fc10.i386.rpm) = 10267 And thats not my biggest problem. As I suspected the linux sites have removed the rpm, so I have to either find it on a host somewhere or host it myself. My goal is to somehow prepend MASTERSITES to look to my host first, then one of the linux sites, then a backup host? and hopefully one will hit if mine is down for whatever reason. Has anyone had any experience with rpm.pbone.net? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Sat, 07 Jan 2012 12:46:54 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
Ok, clean slate. Lets start afresh :)
First I need a way to test properly. Alex, you mention I need a ports
tree on the machine, and then you say to create a directory somewhere
and put Makefile in it and run make (as root). Does the directory
need to be in the ports tree then?
The ports tree is needed to access bsd.*.mk and maybe some
dependencies. The directory where you test the makefile does not need
to be in the ports tree, but it can be in the ports tree.
The rpm files extracted: is there anyway to distinguish which files
are copied or is it simply put into LINUXBASE wholesale? I ask
It is copied completely. But you can delete whatever you want in
a post-extract target:
---snip---
post-extract:
@${RM} ${WRKSRC}/subdir/file1 ${WRKSRC}/subdir/file2
---snip---
because the rpm in question contains pam libraries which are unneeded
obviously as authentication is done by the host? system. I believe
this could represent a bit of a security risk, but I suppose one
could setup an option if wanted.
And how does this affect PLIST?
You should add all the files which get installed into the plist.
And by running make a port is normally built in the port's directory.
In the case of a linux port it is only downloaded into the
distfiles/. Is it extracted during make or make install though? I
couldn't quite determine that categorically.
make extract will extract it. If you type make, make extract will
be executed automatically if needed.
I've also changed the Makefile to use bsd.linux-rpm.mk instead of
bsd.port.mk.
That's wrong. bsd.port.mk is needed and includes bsd.linux-rpm.mk if
needed automatically.
I have setup a pkg-descr file to be put in the directory.
Hosting: I downloaded the rpm myself (including srpm), and I can host
them and maybe arrange for them to be hosted elsewhere as well. Can I
use MASTER_SITES to append/prepend? I also have to untangle the web
of how to determine which file to download - argh hem! Sorry, fetch ;)
If they are not available from the default fedora 10 master site (and
most likely this will be the case), just MASTER_SITES to whatever site
contains the file. If it is only your site... maybe bad luck for your
bandwith. If they are available somewhere else, use a sensible default.
if the linux-f10 base ports are obtained from the Fedora sites, then
what happens if f10 rpms are no longer available there?
They aren't anymore, we already have them on FreeBSD servers
(CRITICAL is a shortcut for a set of the FreeBSD servers).
And finally checksums: I create a checksum for the port, the linux
sites have checksums, and I was advised in passing to check the
checksums match. The checksums are going to differ aren't they? Linux
and BSD checksums wouldn't be the same, surely?
The make makesum will generate the FreeBSD checksum, it is
ok/recommended to create the FreeBSD checksums this way. The advise you
got was to check if there is a checksum or cryptographic signature for
packages available, and to check them by hand (to verify that what you
got is really what it is supposed to be) before submitting a port.
If the checksums are generated the same way on FreeBSD as for the
upstream distfile, well, in this case the verification by hand is
simple, you just compare if the checksums are the same. If it is a
different checksum, you need to find a way to calculate the same
checksum on FreeBSD (bu you don't include it in the port), and then you
compare the checksums. That's all.
Bye,
Alexander.
--
http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 6 January 2012 21:16, Alexander Leidinger alexan...@leidinger.net wrote: The linux ports are a little bit special. They are binary ports and the GPL requires that we distribute the source too. Really? That's not how I read the GPL, nor its interpretation: http://www.gnu.org/licenses/gpl-faq.html#WhatDoesWrittenOfferValid Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Sat, Jan 07, 2012 at 08:31:04PM +, Chris Rees wrote: On 6 January 2012 21:16, Alexander Leidinger alexan...@leidinger.net wrote: The linux ports are a little bit special. They are binary ports and the GPL requires that we distribute the source too. Really? That's not how I read the GPL, nor its interpretation: http://www.gnu.org/licenses/gpl-faq.html#WhatDoesWrittenOfferValid The Linux ports are a little bit special. They are binary ports and the GPL requires offers of source along with distribution of binaries. This is most easily accomplished, in our case, by providing source code downloads alongside the binary downloads. Is that better? In effect, it's the same thing, but longer. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 21:18, Gary Jennejohn wrote:
On Thu, 05 Jan 2012 09:52:40 +1000
Da Rockfreebsd-po...@herveybayaustralia.com.au wrote:
On 01/04/12 23:27, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000
Da Rockfreebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.includebsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
Ok, thats good so far then. Thanks for the assessment.
Now, what's portlint?
/usr/ports/ports-mgmt/portlint. It does syntax checking on the Makefile
and checks things like correct checksums in distfile. You run it in the
port's directory.
And I have a question or two about the rpm. Do I need to script
something to just extract the files needed, or is it already in the mk
files already somewhere?
I suspect that setting USE_LINUX_RPM= yes in Makefile should be all
you need, but I've never done a RPM port. Some seem to use only
LINUX_RPM_ARCH= i386, which is the only option at the moment since
we don't have a AMD64 Linux base port.
And how do I work out the url for fetching the rpm? This particular one
is a moving target as the distro is already eol. Is it stored on the
FreeBSD servers? Or what do I do here?
That could be a problem. Maybe a committer could host it for you. I'm
hosting flwm-1.00.tgz, although I don't think it's used anymore.
In the porters handbook it mentions checksums and make makesum - does
that mean I have to put it in the ports tree to try it?
I just update Makefile, fetch the tarball and then run make makesum
before generating diffs or making a tarball of the port.
And is pkg-message scripted or do I just create it?
See the comment in /usr/ports/Mk/bsd.port.mk. There are lots of very
informative comments in that file.
I've read that before too, but I seem to be missing something
fundamental about ports here. I need to get a handle on all this before
I can proceed. I'm pulling it apart now, anyway.
There are native ports, and there are the linux base ports. For the
native ports the maintainer hosts? But these linux ports are they hosted
on the linux rpm sites? Or are they hosted by the maintainer? So I
believe I cannot sort a few things out until I know exactly what is
going on here. As I mentioned its eol, but if the rest come from the
linux sites...
All I want is 3 files from the usr/lib in the rpm (I think). What I
couldn't quite ascertain is what is done here in the bsd.linux-rpm.mk:
is it extracted and the files copied by make? Or is the rpm installed as
in linux?
If I have to find a host for it I can host it, but what opportunities
for a backup site exist in case of failure? Do I have to arrange that as
the maintainer, or is it mirrored by FreeBSD automatically? Ideally I
suppose both those scenarios would be in order.
And Chris, the license to most linux core stuff is GPL - I also checked
the COPYING file for nss_ldap (as that is the only one we're concerned
with here) and its GPLv2.
I've been spending the past few days trying to work out a tinderbox but
my resources are stretched. I'm hoping to rectify this in the near
future, but so far nada...
The checksums are all tied up with the hosting and so I'm still stuck
there until I work it out, Paul. So I have to untangle these threads so
I have a clearer picture on what I'm doing. from what I understand in
what you're telling me it means I have to create the checksums to make
available from the site, and makesum downloads it. If thats right, what
do I have to do to create them? The handbook says differently (I think?
Maybe I'm reading it wrong...)
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 06/01/2012 14:33, Da Rock wrote: There are native ports, and there are the linux base ports. For the native ports the maintainer hosts? But these linux ports are they hosted on the linux rpm sites? Or are they hosted by the maintainer? So I believe I cannot sort a few things out until I know exactly what is going on here. As I mentioned its eol, but if the rest come from the linux sites... The fact that some ports are linux-base ports and some are native is not that significant. The important differences are that: * the linux ports install into PREFIX=/compat/linux and the native ports generally use PREFIX=/usr/local * you don't compile the linux ports from source; instead you just unpack pre-compiled binaries from one or other of the Linux packaging systems. Who hosts the distfiles depends entirely on circumstance. If there's an active project that has the distfile freely available for download, then use that. Otherwise you will have to find a server somewhere you could make the distfiles available from. That should be distinct from the distfile cache generated by the ports building cluster. This is the same irrespective of whether it is a linux-base or a native port. All I want is 3 files from the usr/lib in the rpm (I think). What I couldn't quite ascertain is what is done here in the bsd.linux-rpm.mk: is it extracted and the files copied by make? Or is the rpm installed as in linux? bsd.linux-rpm.mk provides a customized version of the do-install make target, and all the necessary bits to extract the files from the .rpm, so yes. However, it does assume packages are downloaded from one of the well-known FTP sites for (in your case) Fedora 10, so you'll have to override that bit by setting MASTER_SITES etc. yourself. If I have to find a host for it I can host it, but what opportunities for a backup site exist in case of failure? Do I have to arrange that as the maintainer, or is it mirrored by FreeBSD automatically? Ideally I suppose both those scenarios would be in order. More than one download site is desirable, but not an absolute requirement. Unless the license terms say otherwise, the distfiles will end up being mirrored on ftp.freebsd.org but this doesn't count towards the number of available download sites. I've been spending the past few days trying to work out a tinderbox but my resources are stretched. I'm hoping to rectify this in the near future, but so far nada... http://redports.org/wiki/UserGuide It's only just been opened to public use, but it seems to be being received with great gladness so far. The checksums are all tied up with the hosting and so I'm still stuck there until I work it out, Paul. So I have to untangle these threads so I have a clearer picture on what I'm doing. from what I understand in what you're telling me it means I have to create the checksums to make available from the site, and makesum downloads it. If thats right, what do I have to do to create them? The handbook says differently (I think? Maybe I'm reading it wrong...) Usually the process is that you edit the Makefile to see up the PORTNAME, PORTVERSION or DISTVERSION, MASTER_SITES and anything else to do with downloading the distfile. Then you just run 'make makesum' That should download the distfile, calulate the SHA256 checksum and write out a suitable distinfo file automatically. If there are out-of-band mechanisms for checking the integrity of the distfile, then you as maintainer should certainly check them. (eg. digital signatures on distfiles or published checksums) However, once you've done that then the SHA265 checksum in distinfo should be sufficient to ensure all ports users are downloading the same, correct, content. Either that or maybe I'm just too tired rather than confused... :/ I'll have a look at another linux port tomorrow and pull it apart- and I'll try one closer to the core this time. Yep. Blatantly copying from a similar and well-written port is the best method, and definitely approved of. Watch out for older ports though -- best practice has changed over time, and not all ports have been updated to match. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 6 Jan 2012 14:37, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: If I have to find a host for it I can host it, but what opportunities for a backup site exist in case of failure? Do I have to arrange that as the maintainer, or is it mirrored by FreeBSD automatically? Ideally I suppose both those scenarios would be in order. And Chris, the license to most linux core stuff is GPL - I also checked the COPYING file for nss_ldap (as that is the only one we're concerned with here) and its GPLv2. Thanks for checking. When it comes to licensing, one should never make assumptions :) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Sat, 07 Jan 2012 00:33:30 +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 01/05/12 21:18, Gary Jennejohn wrote: [snip lots of old stuff] There are native ports, and there are the linux base ports. For the native ports the maintainer hosts? But these linux ports are they hosted on the linux rpm sites? Or are they hosted by the maintainer? So I believe I cannot sort a few things out until I know exactly what is going on here. As I mentioned its eol, but if the rest come from the linux sites... Usually the RPM is grabbed from one of the many Linux sites, assuming it's still hosted on one. Once the port gets into the tree, and assuming it can still be grabbed from a Linux site, then it will eventually end up under distfiles on one of the FreeBSD sites. The FreeBSD sites are usually the last resort for getting distfiles. All I want is 3 files from the usr/lib in the rpm (I think). What I couldn't quite ascertain is what is done here in the bsd.linux-rpm.mk: is it extracted and the files copied by make? Or is the rpm installed as in linux? I must admit that I'm not too clear on how this works myself. If I have to find a host for it I can host it, but what opportunities for a backup site exist in case of failure? Do I have to arrange that as the maintainer, or is it mirrored by FreeBSD automatically? Ideally I suppose both those scenarios would be in order. Already answered above. The checksums are all tied up with the hosting and so I'm still stuck there until I work it out, Paul. So I have to untangle these threads so I have a clearer picture on what I'm doing. from what I understand in what you're telling me it means I have to create the checksums to make available from the site, and makesum downloads it. If thats right, what do I have to do to create them? The handbook says differently (I think? Maybe I'm reading it wrong...) I think Paul was assuming that the hosting Linux site will provide the checksums. You have to make sure that they agree with what makesum generates in distinfo. -- Gary Jennejohn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, 5 Jan 2012 12:18:25 +0100 Gary Jennejohn gljennj...@googlemail.com wrote: On Thu, 05 Jan 2012 09:52:40 +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: And I have a question or two about the rpm. Do I need to script something to just extract the files needed, or is it already in the mk files already somewhere? I suspect that setting USE_LINUX_RPM= yes in Makefile should be all you need, but I've never done a RPM port. Some seem to use only More or less correct. He already has his Makefile nearly at the minimum. And how do I work out the url for fetching the rpm? This particular one is a moving target as the distro is already eol. Is it stored on the FreeBSD servers? Or what do I do here? That could be a problem. Maybe a committer could host it for you. I'm hosting flwm-1.00.tgz, although I don't think it's used anymore. If it is not available on the Fedora 10 sites, you can host it on your system, or someone can offer to host it for you. We can arrange to host it on FreeBSD systems, I already have some linux ports there. In the porters handbook it mentions checksums and make makesum - does that mean I have to put it in the ports tree to try it? I just update Makefile, fetch the tarball and then run make makesum before generating diffs or making a tarball of the port. The linux ports are a little bit special. They are binary ports and the GPL requires that we distribute the source too. So if the RPM and the SRPM follow the distribution-default-naming-convention, you should run make -DPACKAGE_BULDING makesum and it will also take care about the SRPM. Without this we can not really integrate it into the ports tree (and the package building cluster will spit out errors). If it does not follow the naming convention, you have to override it (if you set DISTFILES, you need to set SRC_DISTFILES manually, you have to set MASTER_SITE_SRC_SUBDIR if you set MASTER_SITE_SUBDIR). bsd.linux-rpm.mk has the corresponding code. And is pkg-message scripted or do I just create it? See the comment in /usr/ports/Mk/bsd.port.mk. There are lots of very informative comments in that file. If you do not want to use variable-expansion in it, you just create it. Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, 05 Jan 2012 10:42:17 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
On 01/05/12 07:10, Alexander Leidinger wrote:
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port
and I would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so
I've used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:
archivers/linux-f10-nss_ldap # Date created:
2012-01-04 # Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=
CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10- DISTNAME=
${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
This should be you (if you're willing to maintain the port).
You keep dropping hints like this all the time Alex :)
Honestly, though, I'm not sure whats involved or whether I'm capable
of handling the responsibility. This one is not likely to change too
much over time, but my skills are probably wanting.
More or less everyone started like this. Just jump in and give it a
try. As you can see we have some helpful people here around.
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
This does not sound like you took a Fedora 10 RPM here, but you
specified in LINUX_DIST_VER that you use Fedora 10.
I wasn't sure exactly what to put there yet, but this was a Makefile
for linux-f10-ucl so I thought it would be at least close. The
filename is supposed to be nss_ldap-264-6.fc10.i386.rpm.
I suggest to grep around Mk/*linux* for such linux-specific stuff. Most
likely you will find places where they are used. Maybe you can deduvt
from there if they are needed in your Makefile, or to what they should
be set to.
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2
usr/lib/libnss_ldap.so usr/lib/libnss_ldap-264.so DOCSDIR=
${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO DESCR=
${.CURDIR}/../${PORTNAME}/pkg-descr
You don't need DESCR this way, it looks like this sets it to the
same file (but in a different way) than the default value of DESCR.
I have a pkg-descr file setup. That should be right, isn't it?
Yes. You only need to change the value of DESCR in the Makefile, if you
want to use another (generated) file.
.includebsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as
well.
When doing the make makesum, please use make -DPACKAGE_BUILDING
makesum to get the checkums of the SRPMs recorded too. We are
obliged to provide the GNU sources the same way like the binaries,
and IIRC we have some logic which fetches the SRPMs on tha packaga
bulding cluster.
Oh, dear. I'll have to go hunting for them then.
Unfortunately yes.
Bye,
Alexander.
--
http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, 4 Jan 2012 20:19:55 -0700 Chad Perrin c...@apotheon.net wrote: On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: On 01/05/12 12:11, Chad Perrin wrote: The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? Ask on this list, I guess. Hey -- does anyone (qualified) want to mentor Da Rock as a port maintainer? I suggest to just ask on the list when there are questions. I expect that people with specific questions get much faster responses from the list than from a single person. Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Fri, 6 Jan 2012 17:24:50 +0100 Gary Jennejohn gljennj...@googlemail.com wrote: On Sat, 07 Jan 2012 00:33:30 +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: All I want is 3 files from the usr/lib in the rpm (I think). What I couldn't quite ascertain is what is done here in the bsd.linux-rpm.mk: is it extracted and the files copied by make? Or is the rpm installed as in linux? I must admit that I'm not too clear on how this works myself. The files from the RPM are extracted and then copied to the LINUXBASE (if not overridden). If the Makefiles species some files to brand (should be done for executable binaries, not for libs) the files are branded before installation. See bsd.linux-rpm.mk, do-install target. Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Sat, 07 Jan 2012 00:33:30 +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 01/05/12 21:18, Gary Jennejohn wrote: See the comment in /usr/ports/Mk/bsd.port.mk. There are lots of very informative comments in that file. I've read that before too, but I seem to be missing something fundamental about ports here. I need to get a handle on all this before I can proceed. I'm pulling it apart now, anyway. The linux ports are far from normal FreeBSD ports. There are two levels of indirections involved. The ports which make up the linux infrastructure ports (USE_LINUX_APPS=xxx; defined in bsd.linux-apps.mk... you don't need it for your port I think) - typically ports which are needed by several other linux ports - are similar to e.g. GNOME ports, but they don't use bsd.port.mk like the other FreeBSD ports, but the bsd.linux-rpm.mk. And bsd.linux-rpm.mk uses bsd.ports.mk. bsam@ and me wrote those linux mk files, and at least I need to consult the files if I review a linux port more often than if I review a normal FreeBSD port. So if you don't get it the first time, don't be afraid, you didn't chose to make one of the most easy ports. Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, 05 Jan 2012 09:52:40 +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: In the porters handbook it mentions checksums and make makesum - does that mean I have to put it in the ports tree to try it? You need to have the ports tree on the machine where you try it. Just create a directory somewhere, copy the Makefile inside, and give it a try (most easy as root, this way you don't have to override some directory variables to get it working). Before you try the redports suggestions: get it first working via a simple make on a local system first. If you only use redports it would slow you down until you get something working. Bye, Alexander. -- http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
Ok, clean slate. Lets start afresh :) First I need a way to test properly. Alex, you mention I need a ports tree on the machine, and then you say to create a directory somewhere and put Makefile in it and run make (as root). Does the directory need to be in the ports tree then? The rpm files extracted: is there anyway to distinguish which files are copied or is it simply put into LINUXBASE wholesale? I ask because the rpm in question contains pam libraries which are unneeded obviously as authentication is done by the host? system. I believe this could represent a bit of a security risk, but I suppose one could setup an option if wanted. And how does this affect PLIST? And by running make a port is normally built in the port's directory. In the case of a linux port it is only downloaded into the distfiles/. Is it extracted during make or make install though? I couldn't quite determine that categorically. I've also changed the Makefile to use bsd.linux-rpm.mk instead of bsd.port.mk. I have setup a pkg-descr file to be put in the directory. Chris, you're right about the license situation. I nearly fell for it: ass-u-me... :) Hosting: I downloaded the rpm myself (including srpm), and I can host them and maybe arrange for them to be hosted elsewhere as well. Can I use MASTER_SITES to append/prepend? I also have to untangle the web of how to determine which file to download - argh hem! Sorry, fetch ;) if the linux-f10 base ports are obtained from the Fedora sites, then what happens if f10 rpms are no longer available there? And finally checksums: I create a checksum for the port, the linux sites have checksums, and I was advised in passing to check the checksums match. The checksums are going to differ aren't they? Linux and BSD checksums wouldn't be the same, surely? I'll keep at it in the meantime... :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, 05 Jan 2012 09:52:40 +1000
Da Rock freebsd-po...@herveybayaustralia.com.au wrote:
On 01/04/12 23:27, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000
Da Rockfreebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=
CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.includebsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
Ok, thats good so far then. Thanks for the assessment.
Now, what's portlint?
/usr/ports/ports-mgmt/portlint. It does syntax checking on the Makefile
and checks things like correct checksums in distfile. You run it in the
port's directory.
And I have a question or two about the rpm. Do I need to script
something to just extract the files needed, or is it already in the mk
files already somewhere?
I suspect that setting USE_LINUX_RPM= yes in Makefile should be all
you need, but I've never done a RPM port. Some seem to use only
LINUX_RPM_ARCH= i386, which is the only option at the moment since
we don't have a AMD64 Linux base port.
And how do I work out the url for fetching the rpm? This particular one
is a moving target as the distro is already eol. Is it stored on the
FreeBSD servers? Or what do I do here?
That could be a problem. Maybe a committer could host it for you. I'm
hosting flwm-1.00.tgz, although I don't think it's used anymore.
In the porters handbook it mentions checksums and make makesum - does
that mean I have to put it in the ports tree to try it?
I just update Makefile, fetch the tarball and then run make makesum
before generating diffs or making a tarball of the port.
And is pkg-message scripted or do I just create it?
See the comment in /usr/ports/Mk/bsd.port.mk. There are lots of very
informative comments in that file.
--
Gary Jennejohn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 5 Jan 2012 04:13, Janketh Jay jan...@unfs.us wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys! On 01/04/2012 08:19 PM, Chad Perrin wrote: On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: On 01/05/12 12:11, Chad Perrin wrote: The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? Ask on this list, I guess. Hey -- does anyone (qualified) want to mentor Da Rock as a port maintainer? As much as I hate to toss Chris Rees under the bus on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a mentor, I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... I'll answer any questions to the list that I can ;) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 4 Jan 2012 23:58, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 01/05/12 01:41, Chad Perrin wrote: On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote: On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I was advised to copy the essential parts from a similar port, so I've used archivers/linux-f10-ucl. This is my Makefile: [snip] Doesn't pass portlint. Can't fetch the RPM file. Otherwise, a pretty good start. It also lacks license information. How do I set that? Its linux so its GPL. What??? Licensing is up to the individual projects, not the kernel! Can you double-check the choice? There'll be a COPYING file on the tarball or similar. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
--On January 5, 2012 12:22:45 PM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: Ok. I've been working through the handbook step by step, and I'm stuck at checksums so I probably haven't yet reached that part yet. I'll check it out now To get the checksums, type make fetch to download the packages and then make makesum to get the checksums. This is a critical step for a port. You need to make sure the checksum matches what the site says it should be, because everyone who builds that port will be expecting that to be correct. They're counting on that checksum to ensure that they don't download a compromised copy of the software. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
linux-f10-nss_ldap: my first port - be gentle :)
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.include bsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Cheers
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, 04 Jan 2012 22:31:51 +1000
Da Rock freebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.include bsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
--
Gary Jennejohn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote: On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I was advised to copy the essential parts from a similar port, so I've used archivers/linux-f10-ucl. This is my Makefile: [snip] Doesn't pass portlint. Can't fetch the RPM file. Otherwise, a pretty good start. It also lacks license information. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/04/12 23:27, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000
Da Rockfreebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.includebsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
Ok, thats good so far then. Thanks for the assessment.
Now, what's portlint?
And I have a question or two about the rpm. Do I need to script
something to just extract the files needed, or is it already in the mk
files already somewhere?
And how do I work out the url for fetching the rpm? This particular one
is a moving target as the distro is already eol. Is it stored on the
FreeBSD servers? Or what do I do here?
In the porters handbook it mentions checksums and make makesum - does
that mean I have to put it in the ports tree to try it?
And is pkg-message scripted or do I just create it?
Thanks again.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 07:10, Alexander Leidinger wrote:
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port
and I would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so
I've used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES= CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME= ${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
This should be you (if you're willing to maintain the port).
You keep dropping hints like this all the time Alex :)
Honestly, though, I'm not sure whats involved or whether I'm capable of
handling the responsibility. This one is not likely to change too much
over time, but my skills are probably wanting.
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
This does not sound like you took a Fedora 10 RPM here, but you
specified in LINUX_DIST_VER that you use Fedora 10.
I wasn't sure exactly what to put there yet, but this was a Makefile for
linux-f10-ucl so I thought it would be at least close. The filename is
supposed to be nss_ldap-264-6.fc10.i386.rpm.
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
You don't need DESCR this way, it looks like this sets it to the same
file (but in a different way) than the default value of DESCR.
I have a pkg-descr file setup. That should be right, isn't it?
.includebsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
When doing the make makesum, please use make -DPACKAGE_BUILDING
makesum to get the checkums of the SRPMs recorded too. We are obliged
to provide the GNU sources the same way like the binaries, and IIRC we
have some logic which fetches the SRPMs on tha packaga bulding cluster.
Oh, dear. I'll have to go hunting for them then.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, Jan 05, 2012 at 09:53:25AM +1000, Da Rock wrote:
On 01/05/12 01:41, Chad Perrin wrote:
On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
[snip]
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
It also lacks license information.
How do I set that? Its linux so its GPL.
This is an example from /usr/ports/x11/xsel-conrad/Makefile:
LICENSE=xsel-conrad
LICENSE_GROUPS= COPYFREE
LICENSE_NAME= xsel-conrad license
LICENSE_FILE= ${WRKSRC}/COPYING
LICENSE_PERMS= auto-accept dist-mirror dist-sell pkg-mirror pkg-sell
I'm not sure it's perfect port maintainer Makefile practice, but it
works, and it's a lot better than no license information at all in my
opinion. I'd suggest checking that Makefile to see where in the Makefile
to put it.
. . . and if anyone who is more knowledgeable about this stuff than I am
sees something wrong with that Makefile, please let me know.
--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, Jan 05, 2012 at 10:42:17AM +1000, Da Rock wrote: On 01/05/12 07:10, Alexander Leidinger wrote: This should be you (if you're willing to maintain the port). You keep dropping hints like this all the time Alex :) Honestly, though, I'm not sure whats involved or whether I'm capable of handling the responsibility. This one is not likely to change too much over time, but my skills are probably wanting. The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 12:11, Chad Perrin wrote: On Thu, Jan 05, 2012 at 10:42:17AM +1000, Da Rock wrote: On 01/05/12 07:10, Alexander Leidinger wrote: This should be you (if you're willing to maintain the port). You keep dropping hints like this all the time Alex :) Honestly, though, I'm not sure whats involved or whether I'm capable of handling the responsibility. This one is not likely to change too much over time, but my skills are probably wanting. The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 12:08, Chad Perrin wrote:
On Thu, Jan 05, 2012 at 09:53:25AM +1000, Da Rock wrote:
On 01/05/12 01:41, Chad Perrin wrote:
On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
[snip]
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
It also lacks license information.
How do I set that? Its linux so its GPL.
This is an example from /usr/ports/x11/xsel-conrad/Makefile:
LICENSE=xsel-conrad
LICENSE_GROUPS= COPYFREE
LICENSE_NAME= xsel-conrad license
LICENSE_FILE= ${WRKSRC}/COPYING
LICENSE_PERMS= auto-accept dist-mirror dist-sell pkg-mirror pkg-sell
I'm not sure it's perfect port maintainer Makefile practice, but it
works, and it's a lot better than no license information at all in my
opinion. I'd suggest checking that Makefile to see where in the Makefile
to put it.
Ok. I've been working through the handbook step by step, and I'm stuck
at checksums so I probably haven't yet reached that part yet. I'll check
it out now
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: On 01/05/12 12:11, Chad Perrin wrote: The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? Ask on this list, I guess. Hey -- does anyone (qualified) want to mentor Da Rock as a port maintainer? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys! On 01/04/2012 08:19 PM, Chad Perrin wrote: On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: On 01/05/12 12:11, Chad Perrin wrote: The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? Ask on this list, I guess. Hey -- does anyone (qualified) want to mentor Da Rock as a port maintainer? As much as I hate to toss Chris Rees under the bus on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a mentor, I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Other than that, I can always help out as much as I can with questions if you want to email me directly about your port. I know the ins-and-outs about porting and I'd be more than happy to lend a hand. Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8FI1MACgkQGK3MsUbJZn6WcwCeNZykh5WFpdVHhrlpmyqDd1Qn Hb0AnjDVIKpx/9BCiQt9U2pPh6QV9oKs =2XFi -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, Jan 4, 2012 at 11:13 PM, Janketh Jay jan...@unfs.us wrote: As much as I hate to toss Chris Rees under the bus on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a mentor, I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Or just continue to ask on this mailing list. No need to bug specific people when you could get everyone to answer you. You could also pop by on #bsdports on EFNet. A lot of us hang out there. -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 14:13, Janketh Jay wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys! On 01/04/2012 08:19 PM, Chad Perrin wrote: On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: On 01/05/12 12:11, Chad Perrin wrote: The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? Ask on this list, I guess. Hey -- does anyone (qualified) want to mentor Da Rock as a port maintainer? As much as I hate to toss Chris Rees under the bus on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a mentor, I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Other than that, I can always help out as much as I can with questions if you want to email me directly about your port. I know the ins-and-outs about porting and I'd be more than happy to lend a hand. Regards, Janky Jay, III Thanks Jay. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 14:15, Eitan Adler wrote: On Wed, Jan 4, 2012 at 11:13 PM, Janketh Jayjan...@unfs.us wrote: As much as I hate to toss Chris Rees under the bus on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a mentor, I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Or just continue to ask on this mailing list. No need to bug specific people when you could get everyone to answer you. You could also pop by on #bsdports on EFNet. A lot of us hang out there. Oh you can be sure I'll be doing that :) I'm only just starting IRC (if thats what you mean there), but I'll drop in once I'm configured. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Rock, On 01/04/2012 09:24 PM, Da Rock wrote: On 01/05/12 14:15, Eitan Adler wrote: On Wed, Jan 4, 2012 at 11:13 PM, Janketh Jayjan...@unfs.us wrote: As much as I hate to toss Chris Rees under the bus on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a mentor, I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Or just continue to ask on this mailing list. No need to bug specific people when you could get everyone to answer you. You could also pop by on #bsdports on EFNet. A lot of us hang out there. Oh you can be sure I'll be doing that :) I'm only just starting IRC (if thats what you mean there), but I'll drop in once I'm configured. Yup. IRC is correct. EFNet is pretty helpful in the right channels (I would advise staying away from the dingleberries in the I art better than thou channels. :) .) You'll certainly get help in #bsdports, though. Also, might I recommend Irssi as an IRC client. \o/ Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8FKY0ACgkQGK3MsUbJZn4iXgCfRl+oaGJKXp2NFDWe8GPJoo84 cbcAn2C6BMtBjvwf8kFcwlGr9GfmA1l2 =9Ss8 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 22 January 2011 16:28, Chris Rees utis...@gmail.com wrote: On 22 January 2011 15:13, Jan Henrik Sylvester m...@janh.de wrote: The DATADIR whines are addressed in this patch, have a look: http://www.bayofrum.net/~chris/patches/xournal-pkg-plist.diff Thanks, but since the port does not honor DATADIR, it should not be there -- or the DATADIR case must be fixed first. Addressed below. That's all I had time to look at at the moment, perhaps others can help! Alright, came back and now the patch has the desktop-install target defined instead of using the post-install. This is reflected in the patch linked above ^^^ Thanks, I was looking for something like that, but it should be INSTALL_TARGET= install desktop-install, because desktop-install does not include install. Certainly. Looks as though we should define the do-install: target rather than rely on the provided ones; this means that we can make the port DATADIR safe. I'll look shortly. I've stuck it in my Tinderbox for testing, follow it here: http://tinderbox.bayofrum.net/index.php?action=describe_portid=196 Thanks! I do not know Tinderbox enough to understand, why your mkfontscale build tried to install an outdated version of freetype2. Take a look at the new patch so far; I'm still working on Busybox at the moment, so I'm afraid I can't step too much more through it, but it should give you a little more to work on. I've tidied the REINPLACE lines for you too. http://www.bayofrum.net/~chris/patches/xournal.diff DATADIR-safe appears unnecessary according to the conversation http://www.mailinglistarchive.com/freebsd-ports@freebsd.org/msg08234.html , so I think that this port should be fine as is right now. Try submitting it, it should be fine. Cheers! Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 01/23/2011 11:42, Chris Rees wrote:
Take a look at the new patch so far; I'm still working on Busybox at
the moment, so I'm afraid I can't step too much more through it, but
Just a question about what you did so far: Why the
CONFIGURE_ARGS+=--prefix=${PREFIX}? I have tested with a different
PREFIX before and it was successful -- that is what the second part of
the REINPLACE accomplished. What does your line improve?
Or is it a first step, if I wanted to make the port DATADIR-safe?
it should give you a little more to work on. I've tidied the REINPLACE
lines for you too.
Thanks, that is better to read.
http://www.bayofrum.net/~chris/patches/xournal.diff
DATADIR-safe appears unnecessary according to the conversation
http://www.mailinglistarchive.com/freebsd-ports@freebsd.org/msg08234.html
, so I think that this port should be fine as is right now. Try
submitting it, it should be fine.
That is what I thought and since I would have to patch the source (at
least main.c) and the Mafile(s), I did not consider it to be worse it,
since I do not believe anyone will ever use a different DATADIR for this
port.
That leads to my second question: Is your proposal to replace the
share/xournal in pkg-plist by %%DATADIR%% correct although the port
is not DATADIR-safe? Currently, if DATADIR is set the port ends up to be
installed with wrong +CONTENTS, since the installation ignores DATADIR
being set, but +CONTENTS uses it.
I believe that it is correct what portlint says: If and only if your
port is DATADIR-safe (that is, a user can override DATADIR when building
this port and the port will still work correctly) consider using DATADIR
macro; if you are unsure if this port is DATADIR-safe, then ignore this
warning. Thus, there should not be DATADIR in my pkg-plist as long as
the port is not DATADIR-safe.
Cheers,
Jan Henrik
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 23 January 2011 16:24, Jan Henrik Sylvester m...@janh.de wrote:
On 01/23/2011 11:42, Chris Rees wrote:
Take a look at the new patch so far; I'm still working on Busybox at
the moment, so I'm afraid I can't step too much more through it, but
Just a question about what you did so far: Why the
CONFIGURE_ARGS+=--prefix=${PREFIX}? I have tested with a different PREFIX
before and it was successful -- that is what the second part of the
REINPLACE accomplished. What does your line improve?
Or is it a first step, if I wanted to make the port DATADIR-safe?
it should give you a little more to work on. I've tidied the REINPLACE
lines for you too.
Thanks, that is better to read.
http://www.bayofrum.net/~chris/patches/xournal.diff
DATADIR-safe appears unnecessary according to the conversation
http://www.mailinglistarchive.com/freebsd-ports@freebsd.org/msg08234.html
, so I think that this port should be fine as is right now. Try
submitting it, it should be fine.
That is what I thought and since I would have to patch the source (at least
main.c) and the Mafile(s), I did not consider it to be worse it, since I do
not believe anyone will ever use a different DATADIR for this port.
That leads to my second question: Is your proposal to replace the
share/xournal in pkg-plist by %%DATADIR%% correct although the port is
not DATADIR-safe? Currently, if DATADIR is set the port ends up to be
installed with wrong +CONTENTS, since the installation ignores DATADIR being
set, but +CONTENTS uses it.
I believe that it is correct what portlint says: If and only if your port
is DATADIR-safe (that is, a user can override DATADIR when building this
port and the port will still work correctly) consider using DATADIR macro;
if you are unsure if this port is DATADIR-safe, then ignore this warning.
Thus, there should not be DATADIR in my pkg-plist as long as the port is not
DATADIR-safe.
Perhaps you should ignore the portlint warnings and leave it as
share/xournal then.
If you stick up a PR with it attached, it looked absolutely fine by me
either way!
Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 01/23/2011 17:35, Chris Rees wrote:
On 23 January 2011 16:24, Jan Henrik Sylvesterm...@janh.de wrote:
On 01/23/2011 11:42, Chris Rees wrote:
Take a look at the new patch so far; I'm still working on Busybox at
the moment, so I'm afraid I can't step too much more through it, but
Just a question about what you did so far: Why the
CONFIGURE_ARGS+=--prefix=${PREFIX}? I have tested with a different PREFIX
before and it was successful -- that is what the second part of the
REINPLACE accomplished. What does your line improve?
Or is it a first step, if I wanted to make the port DATADIR-safe?
Should I include that line?
(I have just retested: The port installs to the correct PREFIX without
that line and seems to be working fine.)
I believe that it is correct what portlint says: If and only if your port
is DATADIR-safe (that is, a user can override DATADIR when building this
port and the port will still work correctly) consider using DATADIR macro;
if you are unsure if this port is DATADIR-safe, then ignore this warning.
Thus, there should not be DATADIR in my pkg-plist as long as the port is not
DATADIR-safe.
Perhaps you should ignore the portlint warnings and leave it as
share/xournal then.
Thanks.
BTW: I am going to ignore your capitalization of makefile in the first
line, too, since it is non-capitalized in the porters handbook and 20210
over 240 ports go for the non-capitalized variant.
Cheers,
Jan Henrik
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
If prefix works without the CONFIGURE_ARGS then take it out. I put that line
in when experimenting with making it datadir safe.
The capitalization is my one-person campaign, so I fully expected it to be
ignored!
Chris
Sorry for top-posting, Android won't let me quote, but K-9 can't yet do
threading.
On 23 Jan 2011 16:59, Jan Henrik Sylvester m...@janh.de wrote:
On 01/23/2011 17:35, Chris Rees wrote:
On 23 January 2011 16:24, Jan Henrik Sylvesterm...@janh.de wrote:
On 01/23/2011 11:42, Chris Rees wrote:
Take a look at the new patch so far; I'm still working on Busybox at
the moment, so I'm afraid I can't step too much more through it, but
Just a question about what you did so far: Why the
CONFIGURE_ARGS+=--prefix=${PREFIX}? I have tested with a different
PREFIX
before and it was successful -- that is what the second part of the
REINPLACE accomplished. What does your line improve?
Or is it a first step, if I wanted to make the port DATADIR-safe?
Should I include that line?
(I have just retested: The port installs to the correct PREFIX without
that line and seems to be working fine.)
I believe that it is correct what portlint says: If and only if your
port
is DATADIR-safe (that is, a user can override DATADIR when building this
port and the port will still work correctly) consider using DATADIR
macro;
if you are unsure if this port is DATADIR-safe, then ignore this
warning.
Thus, there should not be DATADIR in my pkg-plist as long as the port is
not
DATADIR-safe.
Perhaps you should ignore the portlint warnings and leave it as
share/xournal then.
Thanks.
BTW: I am going to ignore your capitalization of makefile in the first
line, too, since it is non-capitalized in the porters handbook and 20210
over 240 ports go for the non-capitalized variant.
Cheers,
Jan Henrik
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
Thanks for all your suggestions! Cheers, Jan Henrik ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 21 January 2011 21:46, Jan Henrik Sylvester m...@janh.de wrote: Finally, I found an application worse having that is not in ports and looked simple enough to try: Xournal is my first attempt to create a new port. I followed the handbook and did the basic testing with porttools: There are warnings about considering to use DATADIR if the port was DATADIR-safe, but I do not assume it to be. Moreover, there is a warning about my post-patch line. I think the warning is wrong, but I am unsure about that line anyhow. The desktop-install target in Makefile.in is wrong for FreeBSD, but there is probably a better way to fix it. Is my attempt to use the desktop-install target via post-install correct? Do all the files installed by the post-install target go to the correct locations? Is there anything else I should fix before submitting the port as pr? In case the attachment does not make it to the list, I have placed a copy here: http://www.math.uni-hamburg.de/home/sylvester/xournal.shar The DATADIR whines are addressed in this patch, have a look: http://www.bayofrum.net/~chris/patches/xournal-pkg-plist.diff That's all I had time to look at at the moment, perhaps others can help! Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 22 January 2011 12:53, Chris Rees utis...@gmail.com wrote: On 21 January 2011 21:46, Jan Henrik Sylvester m...@janh.de wrote: Finally, I found an application worse having that is not in ports and looked simple enough to try: Xournal is my first attempt to create a new port. I followed the handbook and did the basic testing with porttools: There are warnings about considering to use DATADIR if the port was DATADIR-safe, but I do not assume it to be. Moreover, there is a warning about my post-patch line. I think the warning is wrong, but I am unsure about that line anyhow. The desktop-install target in Makefile.in is wrong for FreeBSD, but there is probably a better way to fix it. Is my attempt to use the desktop-install target via post-install correct? Do all the files installed by the post-install target go to the correct locations? Is there anything else I should fix before submitting the port as pr? In case the attachment does not make it to the list, I have placed a copy here: http://www.math.uni-hamburg.de/home/sylvester/xournal.shar The DATADIR whines are addressed in this patch, have a look: http://www.bayofrum.net/~chris/patches/xournal-pkg-plist.diff That's all I had time to look at at the moment, perhaps others can help! Alright, came back and now the patch has the desktop-install target defined instead of using the post-install. This is reflected in the patch linked above ^^^ I've stuck it in my Tinderbox for testing, follow it here: http://tinderbox.bayofrum.net/index.php?action=describe_portid=196 Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 01/22/2011 14:04, Chris Rees wrote: On 22 January 2011 12:53, Chris Reesutis...@gmail.com wrote: On 21 January 2011 21:46, Jan Henrik Sylvesterm...@janh.de wrote: Finally, I found an application worse having that is not in ports and looked simple enough to try: Xournal is my first attempt to create a new port. I followed the handbook and did the basic testing with porttools: There are warnings about considering to use DATADIR if the port was DATADIR-safe, but I do not assume it to be. Moreover, there is a warning about my post-patch line. I think the warning is wrong, but I am unsure about that line anyhow. The desktop-install target in Makefile.in is wrong for FreeBSD, but there is probably a better way to fix it. Is my attempt to use the desktop-install target via post-install correct? Do all the files installed by the post-install target go to the correct locations? Is there anything else I should fix before submitting the port as pr? In case the attachment does not make it to the list, I have placed a copy here: http://www.math.uni-hamburg.de/home/sylvester/xournal.shar The DATADIR whines are addressed in this patch, have a look: http://www.bayofrum.net/~chris/patches/xournal-pkg-plist.diff Thanks, but since the port does not honor DATADIR, it should not be there -- or the DATADIR case must be fixed first. That's all I had time to look at at the moment, perhaps others can help! Alright, came back and now the patch has the desktop-install target defined instead of using the post-install. This is reflected in the patch linked above ^^^ Thanks, I was looking for something like that, but it should be INSTALL_TARGET= install desktop-install, because desktop-install does not include install. I've stuck it in my Tinderbox for testing, follow it here: http://tinderbox.bayofrum.net/index.php?action=describe_portid=196 Thanks! I do not know Tinderbox enough to understand, why your mkfontscale build tried to install an outdated version of freetype2. Cheers, Jan Henrik ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Xournal: Please, help me with my first port
On 22 January 2011 15:13, Jan Henrik Sylvester m...@janh.de wrote: The DATADIR whines are addressed in this patch, have a look: http://www.bayofrum.net/~chris/patches/xournal-pkg-plist.diff Thanks, but since the port does not honor DATADIR, it should not be there -- or the DATADIR case must be fixed first. Addressed below. That's all I had time to look at at the moment, perhaps others can help! Alright, came back and now the patch has the desktop-install target defined instead of using the post-install. This is reflected in the patch linked above ^^^ Thanks, I was looking for something like that, but it should be INSTALL_TARGET= install desktop-install, because desktop-install does not include install. Certainly. Looks as though we should define the do-install: target rather than rely on the provided ones; this means that we can make the port DATADIR safe. I'll look shortly. I've stuck it in my Tinderbox for testing, follow it here: http://tinderbox.bayofrum.net/index.php?action=describe_portid=196 Thanks! I do not know Tinderbox enough to understand, why your mkfontscale build tried to install an outdated version of freetype2. Because I was an idiot and forgot to update the ports tree before starting the build Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Xournal: Please, help me with my first port
Finally, I found an application worse having that is not in ports and looked simple enough to try: Xournal is my first attempt to create a new port. I followed the handbook and did the basic testing with porttools: There are warnings about considering to use DATADIR if the port was DATADIR-safe, but I do not assume it to be. Moreover, there is a warning about my post-patch line. I think the warning is wrong, but I am unsure about that line anyhow. The desktop-install target in Makefile.in is wrong for FreeBSD, but there is probably a better way to fix it. Is my attempt to use the desktop-install target via post-install correct? Do all the files installed by the post-install target go to the correct locations? Is there anything else I should fix before submitting the port as pr? In case the attachment does not make it to the list, I have placed a copy here: http://www.math.uni-hamburg.de/home/sylvester/xournal.shar Thanks, Jan Henrik # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering sh file. Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # graphics/xournal # graphics/xournal/pkg-plist # graphics/xournal/pkg-descr # graphics/xournal/distinfo # graphics/xournal/Makefile # echo c - graphics/xournal mkdir -p graphics/xournal /dev/null 21 echo x - graphics/xournal/pkg-plist sed 's/^X//' graphics/xournal/pkg-plist '9b172bb60580b3357f245d535c347f95' Xbin/xournal Xshare/applications/xournal.desktop Xshare/icons/hicolor/scalable/apps/xournal.svg Xshare/icons/hicolor/scalable/mimetypes/gnome-mime-application-x-xoj.svg Xshare/icons/hicolor/scalable/mimetypes/xoj.svg Xshare/mime/packages/xournal.xml Xshare/mimelnk/application/x-xoj.desktop Xshare/xournal/html-doc/manual.html Xshare/xournal/html-doc/pixmaps Xshare/xournal/html-doc/screenshot.png Xshare/xournal/pixmaps/black.png Xshare/xournal/pixmaps/blue.png Xshare/xournal/pixmaps/default-pen.png Xshare/xournal/pixmaps/eraser.png Xshare/xournal/pixmaps/fullscreen.png Xshare/xournal/pixmaps/gray.png Xshare/xournal/pixmaps/green.png Xshare/xournal/pixmaps/hand.png Xshare/xournal/pixmaps/highlighter.png Xshare/xournal/pixmaps/lasso.png Xshare/xournal/pixmaps/lightblue.png Xshare/xournal/pixmaps/lightgreen.png Xshare/xournal/pixmaps/magenta.png Xshare/xournal/pixmaps/medium.png Xshare/xournal/pixmaps/orange.png Xshare/xournal/pixmaps/pencil.png Xshare/xournal/pixmaps/rect-select.png Xshare/xournal/pixmaps/recycled.png Xshare/xournal/pixmaps/red.png Xshare/xournal/pixmaps/ruler.png Xshare/xournal/pixmaps/shapes.png Xshare/xournal/pixmaps/stretch.png Xshare/xournal/pixmaps/text-tool.png Xshare/xournal/pixmaps/thick.png Xshare/xournal/pixmaps/thin.png Xshare/xournal/pixmaps/white.png Xshare/xournal/pixmaps/xoj.svg Xshare/xournal/pixmaps/xournal.png Xshare/xournal/pixmaps/xournal.svg Xshare/xournal/pixmaps/yellow.png X@dirrm share/xournal/pixmaps X@dirrm share/xournal/html-doc X@dirrm share/xournal X@exec %%LOCALBASE%%/bin/update-desktop-database /dev/null || /usr/bin/true X@unexec %%LOCALBASE%%/bin/update-desktop-database /dev/null || /usr/bin/true X@exec %%LOCALBASE%%/bin/update-mime-database %D/share/mime X@unexec %%LOCALBASE%%/bin/update-mime-database %D/share/mime X@dirrmtry share/mimelnk/application X@dirrmtry share/mimelnk X@dirrmtry share/mime/packages X@dirrmtry share/mime X@dirrmtry share/icons/hicolor/scalable/mimetypes X@dirrmtry share/icons/hicolor/scalable/apps X@dirrmtry share/icons/hicolor/scalable X@dirrmtry share/icons/hicolor X@dirrmtry share/icons X@dirrmtry share/applications 9b172bb60580b3357f245d535c347f95 echo x - graphics/xournal/pkg-descr sed 's/^X//' graphics/xournal/pkg-descr '805b216eb83a8fb3d83ce023e5fa4c74' XXournal is an application for notetaking, sketching, keeping a Xjournal using a stylus. It is similar to Microsoft Windows Journal or Xto other alternatives such as Jarnal, Gournal, and NoteLab. X XXournal aims to provide superior graphical quality (subpixel Xresolution) and overall functionality; however it lacks the Xcollaborative features of Jarnal. Since Xournal is still in its early Xdevelopment stages, it may not be fully stable, and some features Xhave not been implemented yet. X XXournal supports annotation of PDF files through the Poppler library; XPDF files, much like paper styles, are loaded as an immutable Xbackground image. X XWWW: http://xournal.sourceforge.net 805b216eb83a8fb3d83ce023e5fa4c74 echo x - graphics/xournal/distinfo sed 's/^X//' graphics/xournal/distinfo 'dbdf531c5f805ea1b755f1dff0d9beb7' XSHA256 (xournal-0.4.5.tar.gz) = a7d7c2cb544451939779276e6e5ee5acc756bd0efb5253de15dc00bfe07755d1 XSIZE (xournal-0.4.5.tar.gz) = 425062 dbdf531c5f805ea1b755f1dff0d9beb7 echo x - graphics/xournal/Makefile sed 's/^X//' graphics/xournal/Makefile '7b6ea3301597bf7d5161b3f76878ae21' X# New ports collection makefile for:
Re: My First Port
--On July 5, 2007 9:21:04 AM -0400 Wesley Shields [EMAIL PROTECTED] wrote: Speaking of difficult ports. I'm working on the upgrade to security/bro. It's a royal PITA. The author hardcodes destinations for everything so that the software doesn't follow FreeBSD conventions at all, *and* there's no master setting that you can alter in configure or the top level Makefile.in file. So, I've had to edit almost every Makefile.in in the distro to get the darn thing to behave. Even the docs don't want to install where they should! Paul, As I mentioned before, I took a stab at this port a while ago and came to the same conclusions. I'll gladly take a look at where you are and see if I can help you out at all. Can you send a patch of where you currently are so I can take a look? Sure, I'd be glad to. The only thing I'm not satisfied with at this point is the installation of broccoli's libraries into /usr/local/share. Libraries should be installed in /usr/local/lib. I'm using USE_LDCONFIG= to specify the location (/usr/local/share), but I really shouldn't have to do that. My problem is, I can't figure out where, in broccoli's configure and/or Makefiles that it's specifying to put the libs in share instead of lib. I've attached a tar'd gzip'd file containing patches for the existing port as well as all the new patch files (in FILESDIR) that I've created to force this thing to install where I want it. Any advice would be appreciated. Part of me says I should be doing all this in the port's Makefile rather than patching all the Makefile.in files, but when I tried that, the software created the directories anyway, even though they were empty. This is, by far, the most irritating port I've ever worked on, but I'm close to getting it done. Once it's done, I'm going to create a devel port for the latest version. All of this work is being done, by request, for another project that is being worked on. I was asked to update/create ports for parts that are required for the project. Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
Re: My First Port
On Wed, Jul 04, 2007 at 12:53:45PM -0500, Paul Schmehl wrote:
--On July 4, 2007 4:49:33 PM +0200 Lars Engels [EMAIL PROTECTED] wrote:
On Wed, Jul 04, 2007 at 09:28:45AM -0400, Michael W. Lucas wrote:
On Tue, Jul 03, 2007 at 04:53:46PM -0500, Paul Schmehl wrote:
good comments deleted
Thanks, Shaun and Paul. I appreciate the help. Changes made,
portlint ran, port re-tested, PR submitted.
Somebody stop me before I port again! :-)
No, Sir!
Porting is fun, so we won't stop you from having fun.
And if you're stuck with a more complicated port, just ask
for help. There are a lot of helpful maintainers and committers
around. :)
Speaking of difficult ports.
I'm working on the upgrade to security/bro. It's a royal PITA. The author
hardcodes destinations for everything so that the software doesn't follow
FreeBSD conventions at all, *and* there's no master setting that you can
alter in configure or the top level Makefile.in file. So, I've had to edit
almost every Makefile.in in the distro to get the darn thing to behave.
Even the docs don't want to install where they should!
Here's my FILESDIR:
ls files/
patch-Makefile.in patch-policy-Makefile.in
patch-aux-scripts-Makefile.in patch-policy-sigs-Makefile.in
patch-configure patch-scripts-Makefile.in
patch-doc-quick-start-Makefile.in patch-scripts-s2b-bro-include-Makefile.in
patch-doc-ref-manual-Makefile.in
patch-scripts-s2b-example-bro-files--Makefile.in
patch-doc-user-manual-Makefile.in patch-src-Makefile.in
{{{sigh}}}
I have one last problem. This software installs another piece of software
named broccoli (don't ask), and for some reason broccoli puts it's lib
files in PREFIX/share. I can't seem to find why it's doing that. I grepped
for libdir and it always appears as EPREFIX/lib, which is correct. If anyone
wants to take a look at this thing and figure it out, I would be grateful.
It's the one last piece I need to get this thing working as expected.
You can download the source here: ftp://bro-ids.org/bro-1.1d-stable.tar.gz
Paul,
As I mentioned before, I took a stab at this port a while ago and came
to the same conclusions. I'll gladly take a look at where you are and
see if I can help you out at all. Can you send a patch of where you
currently are so I can take a look?
-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: My First Port
On Tue, Jul 03, 2007 at 04:53:46PM -0500, Paul Schmehl wrote: good comments deleted Thanks, Shaun and Paul. I appreciate the help. Changes made, portlint ran, port re-tested, PR submitted. Somebody stop me before I port again! :-) ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ Coming Soon: Absolute FreeBSD -- http://www.AbsoluteFreeBSD.com On 5/4/2007, the TSA kept 3 pairs of my soiled undies for security reasons. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: My First Port
On Wed, Jul 04, 2007 at 09:28:45AM -0400, Michael W. Lucas wrote: On Tue, Jul 03, 2007 at 04:53:46PM -0500, Paul Schmehl wrote: good comments deleted Thanks, Shaun and Paul. I appreciate the help. Changes made, portlint ran, port re-tested, PR submitted. Somebody stop me before I port again! :-) No, Sir! Porting is fun, so we won't stop you from having fun. And if you're stuck with a more complicated port, just ask for help. There are a lot of helpful maintainers and committers around. :) Lars pgpjJqFl9Iy28.pgp Description: PGP signature
Re: My First Port
--On July 4, 2007 4:49:33 PM +0200 Lars Engels [EMAIL PROTECTED]
wrote:
On Wed, Jul 04, 2007 at 09:28:45AM -0400, Michael W. Lucas wrote:
On Tue, Jul 03, 2007 at 04:53:46PM -0500, Paul Schmehl wrote:
good comments deleted
Thanks, Shaun and Paul. I appreciate the help. Changes made,
portlint ran, port re-tested, PR submitted.
Somebody stop me before I port again! :-)
No, Sir!
Porting is fun, so we won't stop you from having fun.
And if you're stuck with a more complicated port, just ask
for help. There are a lot of helpful maintainers and committers
around. :)
Speaking of difficult ports.
I'm working on the upgrade to security/bro. It's a royal PITA. The
author hardcodes destinations for everything so that the software doesn't
follow FreeBSD conventions at all, *and* there's no master setting that
you can alter in configure or the top level Makefile.in file. So, I've
had to edit almost every Makefile.in in the distro to get the darn thing
to behave. Even the docs don't want to install where they should!
Here's my FILESDIR:
ls files/
patch-Makefile.in
patch-policy-Makefile.in
patch-aux-scripts-Makefile.in
patch-policy-sigs-Makefile.in
patch-configure
patch-scripts-Makefile.in
patch-doc-quick-start-Makefile.in
patch-scripts-s2b-bro-include-Makefile.in
patch-doc-ref-manual-Makefile.in
patch-scripts-s2b-example-bro-files--Makefile.in
patch-doc-user-manual-Makefile.in
patch-src-Makefile.in
{{{sigh}}}
I have one last problem. This software installs another piece of software
named broccoli (don't ask), and for some reason broccoli puts it's lib
files in PREFIX/share. I can't seem to find why it's doing that. I
grepped for libdir and it always appears as EPREFIX/lib, which is correct.
If anyone wants to take a look at this thing and figure it out, I would be
grateful. It's the one last piece I need to get this thing working as
expected.
You can download the source here:
ftp://bro-ids.org/bro-1.1d-stable.tar.gz
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/
My First Port
Hi, After twelve years in FreeBSD, I've finally come across a piece of software that I need that isn't a port already. The software is mod_auth_xradius, for Apache: http://www.outoforder.cc/projects/apache/mod_auth_xradius/ I went through the porter's guide and made an attempt to build a port. I'm sure it's wrong, so I'm not send-pr-ing it yet. You can find my port at: http://www.blackhelicopters.org/~mwlucas/mod_auth_xradius.tgz While this program is small, Radius authentication for Web sites is one of those things that is absolutely vital for those of us who need it. Having it in-tree would be really nice. I would appreciate any comments, critiques, etc., before I submit this. (Or, if you ports guys would rather I submit it as-is and then tell me all the things I did wrong, I'm OK with that too.) While I'm not a ports guy, I'm willing to try to maintain this. Thanks, ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ Coming Soon: Absolute FreeBSD -- http://www.AbsoluteFreeBSD.com On 5/4/2007, the TSA kept 3 pairs of my soiled undies for security reasons. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: My First Port
On Tue, Jul 03, 2007 at 02:28:34PM -0400, Michael W. Lucas wrote: I would appreciate any comments, critiques, etc., before I submit this. (Or, if you ports guys would rather I submit it as-is and then tell me all the things I did wrong, I'm OK with that too.) While I'm not a ports guy, I'm willing to try to maintain this. A few minor observations: 1) You're missing the standard header block. 2) There's a trailing space on the COMMENT line. 3) Instead of setting EXTRACT_SUFX, we have a special variable for bzip2 files: USE_BZIP2= yes Otherwise, it looks good. Shaun -- Shaun Amott // PGP: 0x6B387A9A A foolish consistency is the hobgoblin of little minds. - Ralph Waldo Emerson ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: My First Port
--On Tuesday, July 03, 2007 14:28:34 -0400 Michael W. Lucas [EMAIL PROTECTED] wrote: Hi, After twelve years in FreeBSD, I've finally come across a piece of software that I need that isn't a port already. The software is mod_auth_xradius, for Apache: http://www.outoforder.cc/projects/apache/mod_auth_xradius/ I went through the porter's guide and made an attempt to build a port. I'm sure it's wrong, so I'm not send-pr-ing it yet. You can find my port at: http://www.blackhelicopters.org/~mwlucas/mod_auth_xradius.tgz While this program is small, Radius authentication for Web sites is one of those things that is absolutely vital for those of us who need it. Having it in-tree would be really nice. I would appreciate any comments, critiques, etc., before I submit this. (Or, if you ports guys would rather I submit it as-is and then tell me all the things I did wrong, I'm OK with that too.) While I'm not a ports guy, I'm willing to try to maintain this. Looks fine to me. You just need to do a few things to the Makefile: Right at the top, put: # New ports collection makefile for:mod_auth_xradius # Date created: 1 Jul 2007 # Whom: mwlucas $FreeBSD$ portlint -A WARN: Makefile: [9]: whitespace before end of line. There should never be any whitespace at the end of lines. FATAL: Makefile: no ports collection makefile for line in comment section. FATAL: Makefile: no Whom line in comment section. FATAL: Makefile: no Date created line in comment section. FATAL: Makefile: no $FreeBSD$ line in comment section. I mentioned these above. WARN: Makefile: only one MASTER_SITE configured. Consider adding additional mirrors. Not applicable in this case. WARN: Makefile: EXTRACT_SUFX has to appear earlier. EXTRACT_SUFX should be moved up to right underneath MASTER_SITES, but you should really use USE_BZIP2 instead. USE_BZIP2= Yes 4 fatal errors and 3 warnings found. When you're building new ports, run portlint(1) to check them for errors. ports-mgmt/portlint Also, this only works with Apache 2.0 or greater, so you should specify that: USE_APACHE= 2.0+ So, your Makefile would look like this instead: # New ports collection makefile for:mod_auth_xradius # Date created: 1 Jul 2007 # Whom: mwlucas # $FreeBSD$ PORTNAME= mod_auth_xradius PORTVERSION=0.4.6 CATEGORIES= www MASTER_SITES= http://www.outoforder.cc/downloads/mod_auth_xradius/ MAINTAINER= [EMAIL PROTECTED] COMMENT=Enables RADIUS authentication USE_APACHE= 2.0+ USE_BZIP2= yes GNU_CONFIGURE= yes PLIST_FILES=libexec/apache22/mod_auth_xradius.so .include bds.port.mk -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/
