Any point to building separate 8.2 and 8.3 packages?
Hi, I currently have some 8.2 and 8.3 servers which I cannot upgrade to 9.0 yet. I am looking at building packages with Poudriere and pkgng for these 8.2/8.3 servers. My question is this: do I need to create separate 8.2 and 8.3 jails on Poudriere and build discreet packages for each of these minor releases, or will packages built for a given 8.X release run on any 8.Y release? In other words, are there any compilation/repackaging requirements of ports/packages when one upgrades from one minor version number to the next? Thanks, -Martin ___ 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"
Poudriere not registering OPTIONS changes?
Hi, I've recently discovered Poudriere and have begun using it to build my own local pkgng PACKAGESITE for my FreeBSD 8 and 9 servers. Based on information I read on the web I was under the impression that whenever a new bulk build was launched, Poudriere would notice any port with changed OPTIONS and rebuild these ports, even if the ports' version number hadn't changed. After building my local port list for the first time I realized that I needed a Samba34 package with ADS support enabled (it is off by default) so I decided to try the OPTIONS change feature; I used Poudriere's 'options' command and modified the OPTIONS for the samba34 port. I then issued a bulk build command; however, even though Poudriere reported "Mounting /var/db/ports from: /usr/local/etc/poudriere.d/options" it did not make any comment about changed options and ended shortly thereafter with no new packages built. I then tried using the 'options' command by specifying a jail and re-issued a bulk build, but got the same result. Have I misunderstood how OPTIONS changes are tracked? Did I make a mistake or omit a crucial step in order to have the OPTIONS changes recognized? Thank you, -Martin System: Poudriere 2.2 on FreeBSD 9.0 ___ 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: Gramps 3.3.0 Final Report
On Wed, Oct 31, 2012 at 8:37 PM, Joseph a Nagy Jr wrote: > Sent to the maintainer and to the ports list because of a complaint that > the maintainer isn't listening to the developers. > > I encountered a bug[0] that caused GRAMPS to crash. I filed a bug report > with the developers as the port built just fine. I got a quick response > (surprisingly) and was pointed toward a second bug[1] with a similar > problem and a possible solution, though that person never got back to them. > > As you can see in my bug report comments, I changed a line in the Makefile: > > -USE_BDB=43 > +USE_BDB=48 > > And instead of > > echo "WITH_BERKELEYDB=db43" >> /etc/make.conf > echo "WITH_BDB_VER=43" >> /etc/make.conf > > I manually changed both to: > > WITH_BERKELEYDB=db48 > WITH_BDB_VER=48 > > and rebuilt py-bsddb. Gramps now works as expected. This should be > updated in ports as soon as possible to avoid future unnecessary bug > reports to the Gramps developers. > > [0]: http://www.gramps-project.org/bugs/view.php?id=6157 > [1]: http://bugs.gramps-project.org/view.php?id=5833#c24451 > Are you interested in taking over maintainership of this port? It seems the current maintainer is no longer interested in maintaining the port. Please send me a diff, reply with a diff, or open a pr, and we can get this fix in. Thanks! -jgh ___ 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: Dropping maintainership of science/gramps!
On 11/01/12 17:19, Anders Troback wrote: I do not use FreeBSD any more (I feel in love with OpenBSD:-)) so please remove me as maintainer of the science/gramps port. I can take it over unless someone else is better suited (and actually uses the program). How do you go about doing this, though? ___ 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: Dropping maintainership of science/gramps!
On 1 November 2012 03:19, Anders Troback wrote: > I do not use FreeBSD any more (I feel in love with > OpenBSD:-)) so please remove me as maintainer of the science/gramps > port. Done. You will be welcome back with open arms should you ever desire. :) -- 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: FreeBSD Port: vtwm-5.4.7_3
Yes, it seems that the default is to enable all possible features, but my point is that it would be a little more intelligent if "minimalist type packages" be built minimally, since that is their intention, their functionality. Some software is clearly "minimalist", and "minimalist users" want it that way. I don't see the good reason to build minimalist type software with "all possible features enabled". I have a modem connection, so I can't download such big packages for fun, but I believe the maintainer of VTWM had rplay disabled by default, at least, I know it was that way at one time, and I know it was his intention for it to be disable by default, at least, at one time. Yes, maybe I can get the source and modify things and compile the port without the option, but - I can't imagine most VTWM users want "rplay" or silly sound effects when they are choosing VTWM for its minimalist design, and I don't see the intelligence of burdening them like that. OK, thanks for the reply. I just wanted to add a viewpoint that seems much more sensible to me, and user friendly. There are dozens of other window managers that have lots of glitter, VTWM users don't want that, or why else would they choose it? I am sure I am not alone in valuing all of your work for FreeBSD - thank you all very much. Chad > > Why is "rplay" being packaged with VTWM? > > VTWM is supposed to be a minimal no-frills > > window manager (I have used it for 15 years) > > and I very much dislike the added dependencies > > for things I don't care to use and violate the > > spirit of VTWM. I wrote the programmer that > > did this hack several years ago when he first > > did it, and he promised he would undo it. > > And now, I see it back again (still using 4.11, > > was thinking of upgrading to 9.1). > > > > Please keep VTWM *minimal*. If someone wants > > fancy things like "network sound", I am sure > > one of the more fancy window managers will do. > > If you build the port you can "make config" to set your resulting install > or pkg to have no sound. The default setting in the Makefile enables > sound. ___ 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"
Dropping maintainership of science/gramps!
I do not use FreeBSD any more (I feel in love with OpenBSD:-)) so please remove me as maintainer of the science/gramps port. Br/Anders ___ 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"
Can not compile freeswitch-core-devel when alsa-lib is intalled
Hello, On my system I have alsa-lib installed. I tried to install freeswitch-core-devel, but it built with error. If I remove alsa-lib, then I able to build and install freeswitch-core-devel. May be it is worth to add alsa-lib to the CONFLICTS ? Best regards, Denis ___ 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"
