Re: Linux compatibility with more than one Linux installed?
> The linux-base port is supposed to provide good integration into FreeBSD. > Ideally the integration is seamless. > The linux-dist ports provide a complete linux environment. You chroot into it > and you have a complete linux system. You can compile linux binaries inside > the > +linux-dist. You can not do this with the linux-base. > Bye, > Alexander. So I guess that's the fundamental difference between linux-base installed to /compat/linux, and linux-dist? So when I build my Linux installation, then I suppose I can mount that partition and chroot into it? Even as nonroot? Even run X Window applications? I think on some platforms, chroot is root-only, but running ls -l /usr/sbin/chroot in FreeBSD 9.0-RC2 -r-xr-xr-x 1 root wheel 7736 Nov 22 11:08 /usr/sbin/chroot Tom ___ 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"
Christmas Secret Savings Inside - Tablet PC USD 69.99
Your email program does not support HTML. To view an online version of this email, please click the link below. http://b.ss38.on9mail.com/new/en_send_preview_iframe2.aspx?SID=37&NewsletterID=87733&SiteID=8971&EmailID=26130253&HitID=1322732638816&token=f28e0363b9e4d14b19b988dbfd00cd983b36ce32 To unsubscribe, click the link below. http://b.ss38.on9mail.com/RWCode/subscribe.asp?SID=37&SiteID=8971&Email=po...@freebsd.org&HitID=1322732638816 ___ 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"
Porting application with RUN_DEPENDS and extra knobs
Hi, I am trying to port one of our Home Brew application for FreeBSD as we are moving towards BSD from Linux. Now while creating the Makefile for creating a port I am in a trouble. I want to automate the full script. My application has RUN_DEPENDS for perl. And perl should be built with PERL_64BITINT, THREADS and USE_PERL knobs for my application to work. Is there any way I can force from my Makefile to build and install perl with the above mentioned knobs. I have thought of creating a patch file and changing the knobs in /var/db/ports//options. But is there any official way to handle this? Thanks in advance. Regards, Moin ___ 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: Porting application with RUN_DEPENDS and extra knobs
On 01/12/2011 19:25, Muhammad Moinur Rahman wrote: > I am trying to port one of our Home Brew application for FreeBSD as we are > moving towards BSD from Linux. Now while creating the Makefile for creating > a port I am in a trouble. I want to automate the full script. My > application has RUN_DEPENDS for perl. And perl should be built with > PERL_64BITINT, THREADS and USE_PERL knobs for my application to work. Is > there any way I can force from my Makefile to build and install perl with > the above mentioned knobs. > > I have thought of creating a patch file and changing the knobs > in /var/db/ports//options. But is there any official way to > handle this? The standard way of doing this is to create a slave port where you can tweak the options settings and enforce whatever you require. Compare, for example, editors/emacs and editors/emacs-nox11. Add a 'CONFLICTS' variable to prevent both the original perl port and your slave copy being installed simultaneously. You don't need to submit this new slave port to be included in the standard ports tree in order to use it with locally created ports. You can locally add a port /usr/ports/foo/bar by adding: /usr/ports/foo/Makefile.local with contents: SUBDIR += bar and then refer to it in port dependencies in the usual way. If you have a bunch of local ports, you can add in a whole new category directory in a similar way by adding a /usr/ports/Makefile.local However, if you do this, be careful about how you manage synching updates to your ports tree. This sort of change (adding files) will persist across csup(1) runs, whereas editing files already part of the ports would not[*]. I think it also works with 'portsnap update' but you'll have to test to make sure. If you wanted to submit your home brew app to the ports, then it might be better to use eg. a PKGREQ script or a small snippet of perl in the Makefile to verify that perl was installed WITH_THREADED = yes and so forth, rather than adding a slave port. Cheers, Matthew [*] If you need to keep locally edited ports -- 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
FreeBSD Port: rt-3.8.11
Hello, Thanks for packaging RT! It appears that Makefile.cpan hasn't been updated from 3.8.8's dependencies to 3.8.11's. Consequently, RT will be broken after moving from 3.8.8 to a newer version. This was discovered while troubleshooting an RT upgrade for a customer whose system didn't have p5-Digest-SHA installed. Running `git log -p rt-3.8.8..rt-3.8.11 sbin/rt-test-dependencies.in` from RT's repo will show you the handful of changes, including a new dep and version bumps. Normally RT's Makefile target testdeps would catch incorrect module versions and missing modules before install, but it appears to be disabled by a packaging patch. If there are still reasons for disabling testdeps during install/upgrade, perhaps testdeps can be run as a packaging sanity check? If it exits with an error, a message could be reported to the user letting them know there may be a problem with the package (hopefully prompting them to file a bug report like this one). Cheers, Thomas ___ 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"
CFR: add an example of manually fetching distfiles to Porter's Handbook
A few people are getting "creative" again on ways to express this common
need. AFAIK the following is the best way to do it. What do people think?
mcl
Index: book.sgml
===
RCS file:
/home/FreeBSD/dcvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v
retrieving revision 1.1119
diff -u -r1.1119 book.sgml
--- book.sgml 4 Nov 2011 14:28:43 - 1.1119
+++ book.sgml 1 Dec 2011 22:26:38 -
@@ -4698,6 +4698,19 @@
/usr/ports/LEGAL for every listed distribution
file, describing exactly what the restriction entails.
+
+
+ Examples
+
+ The preferred way to state "the distfiles for this port must be
+ fetched manually" is as follows:
+.if !exists(${DISTDIR}/${DISTNAME}${EXTRACT_SUFX})
+IGNORE= "may not be redistributed because of licensing reasons. Please
visit some-website to accept their license and
download ${DISTFILES} into ${DISTDIR}"
+.endif
+
+ This both informs the user, and sets the proper metadata on
+ the user's machine for use by automated programs.
+
mcl
___
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"
