On Jul 12, 2008, at 2:56 AM, Mark Linimon wrote:
On Sat, Jul 12, 2008 at 08:18:58AM +0200, Koen Martens wrote:
Silly suggestion: if your business is depending on it, either fix
the port
yourself or pay someone to fix it for you. Seriously, making
demands in a
free software project is silly
On Jul 11, 2008, at 2:53 PM, Remko Lodder wrote:
So, when can I expect your updated work on the port, build all
dependencies to make sure they keep on working etc? I understand
that we want to have this as soon as possible, but also do keep in
mind that we would like to make sure as much a
On Jul 11, 2008, at 10:57 AM, Brandon S. Allbery KF8NH wrote:
On 2008 Jul 11, at 10:31, Vivek Khera wrote:
When I talk to some linux folks they just laugh that we don't have
a perl 5.10 yet. It is embarrassing, actually, to go out and
evangelize FreeBSD when there are delays like
elays like this.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.Khera Communications, Inc.
Internet: [EMAIL PROTECTED] Rockville, MD +1-301-869-4449 x806
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
On Jul 7, 2008, at 9:16 PM, Philip M. Gollucci wrote:
3) I would like to set EXPIRES=NOW()+3 months for www/rt2, www/rt3,
www/rt32.
Leaving www/rt34, www/rt36 where I should either fix the problem and/
or mark them IGNORE until I do.
If this sounds good I'll send a PR in.
+1 on the expi
On Jun 23, 2008, at 3:01 PM, Dale Hagglund wrote:
Thanks for the information. Did you compile via the port, or install
from the pre-built package? Since I have no immediate need for the
java
support that comes with lang/erlang, I uninstalled my modified version
and added erlang-{lite,doc}
On Jun 21, 2008, at 3:48 PM, Dale Hagglund wrote:
Am I missing something obvious here? Should I have been able to build
with the hipe extensions or is this an error in the port makefiles?
erlang-r12b2,1 installed just fine on our 7.0/i386 box a couple of
months ago. It was pulled in as a
On May 14, 2008, at 5:42 AM, Andriy Gapon wrote:
Vivek Khera said:
So you can use *any* SIP client with gizmo for voice, and for
chat, any suitable XMPP (jabber) client. They even give you
instructions on what server settings to use to tie into their
service.
Personally, I use a gizmo
On May 13, 2008, at 3:17 PM, Andriy Gapon wrote:
[this is something similar to skype but SIP based]
So you can use *any* SIP client with gizmo for voice, and for chat,
any suitable XMPP (jabber) client. They even give you instructions on
what server settings to use to tie into their serv
On Apr 21, 2008, at 1:00 PM, Mikhail Teterin wrote:
GraphicsMagick split away for this reasons. Yours,
I just checked into GM. I like the idea of stable API and faster
processing, but how do I convince the port to install the perl
module? I don't see any external perl module for it in p
On Apr 30, 2008, at 4:22 AM, Philip M. Gollucci wrote:
> portname: www/rt3
seriously, who still uses RT 3.0? RT 3.6 is current, and the beta of
the next major version just came out.
___
freebsd-ports@freebsd.org mailing list
http://li
On Apr 24, 2008, at 11:02 AM, Wesley Shields wrote:
It may be overkill but in the past I have run ports-mgmt/portscout to
check for updated versions of ports. I have not run it looking for
perl
That does seem overkill! Thanks for the pointer.
_
On Apr 24, 2008, at 4:53 AM, Lars Balker Rasmussen wrote:
Because my check-updated-modules script was retarded and didn't
understand
that p5-libwww is called libwww-perl on cpan. Fixing, and will be
Is this script something you can share? I maintain about 10 perl
modules for ports and i
Somehow portsnap managed to delete all but /usr/ports/Mk/bsd.port.mk
from my ports/Mk subdir. How to recover without having to start again
from scratch? Can I just copy them from another system? Will it
confuse portsnap?
___
freebsd-ports@freeb
On Mar 3, 2008, at 12:27 PM, Wesley Shields wrote:
I know mail/postfix asks if it should activate itself in
/etc/mail/mailer.conf.
I'll take that as a bug report :-)
Though I'm not sure which way it should default, on BATCH. And does
BATCH apply to package install as well?
On Feb 12, 2008, at 10:17 AM, Conrad J. Sabatier wrote:
The latest portupgrade suddenly seems to have become *very*
unintuitive,
and extremely quirky/buggy. Some of the error/info messages no longer
make any sense at all to me, either!
I have noticed it doesn't chase *any* dependencies tha
On Jan 31, 2008, at 1:35 PM, Paul Schmehl wrote:
One other question. Should the PORTNAME be lower case even though
the DISTNAME is not? Or does it matter?
Portname for perl ports is generally upper/lower case mix as the name
of the perl module itself. I don't think it needs to be smashed
On Jan 31, 2008, at 10:55 AM, Paul Schmehl wrote:
My question is, should I submit this port even though it uses a non-
standard master site from CPAN?
Do it like this:
MASTER_SITES= ${MASTER_SITE_PERL_CPAN}
MASTER_SITE_SUBDIR= ../by-authors/id/S/SA/SAXJAZMAN/Snort
See for example how
On Jan 28, 2008, at 9:47 PM, Doug Barton wrote:
Clement Laforet wrote:
WITH_BERKELEYDB is now deprecated in favor of WITH_BDB in order to
make BDB support consistent with the rest of the ports tree.
Is there a warning generated for users that have the old one
defined? If not it would be a
It seems that the recent changes to the apache20 port Makefile.modules
has broken how I've been configuring my systems.
In my make.conf file I have globally set the following:
WITH_BDB_VER=43
which instructs many ports to use that version of Berkeley DB.
Furtnermore, in my apache configurati
On Jan 22, 2008, at 8:55 PM, Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vivek Khera wrote:
Can I get a little love for ports/119544 and get someone to commit
it?
thanks! It will simplify my deployment process to have it as a
package.
DONE.
thanks
Can I get a little love for ports/119544 and get someone to commit it?
thanks! It will simplify my deployment process to have it as a package.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsu
On Dec 5, 2007, at 8:06 PM, jekillen wrote:
carefully crafting the configuration files for Postfix, I
am informed tha Postfix does not support MySQL tables
as it stands. I have received instruction from Postfix list
about how to add the support:
If you want funny options in your postfix, you
On Dec 4, 2007, at 1:45 PM, Chuck Robey wrote:
Vivek Khera wrote:
On Dec 3, 2007, at 3:40 PM, Chuck Robey wrote:
Need to do some python work, using a lot of FreeBSD's base libs,
and I was wondering, if any ports have swigged the FreeBSD libs?
I'll do it if I must, just trying
On Dec 3, 2007, at 3:40 PM, Chuck Robey wrote:
Need to do some python work, using a lot of FreeBSD's base libs, and
I was wondering, if any ports have swigged the FreeBSD libs? I'll
do it if I must, just trying to save me some work.
Not understanding your use of the word "swigged", all
0
d. Internal record keeping
10
e. Granularity's of the port management system
6
12. Please rate your personal technical skill level?
highly technical.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.Khera Communi
On Dec 3, 2007, at 1:39 AM, Aryeh M. Friedman wrote:
I am purposelly not looking at any previous solutions right now... If
and when it is determined that changes to the current system are
needed I will look at them then for ideas of what has not worked.
(like the Internet or other large complex
On Dec 2, 2007, at 3:54 PM, Miguel Mendez wrote:
I already replied to your questions in private but I wonder if you
took a look at
pkgsrc and the enhancements the OpenBSD people have done the pkg*
commands and whether you think borrowing from them would be useful.
I've been using pkgsrc on
On Nov 27, 2007, at 4:18 AM, [EMAIL PROTECTED] wrote:
Thinking in retrospective - /etc/make.conf was perhaps not the best
place to put USE_APACHE=2.2 when I needed it only for php.
Sure it is a great place to set options...
Try something like this:
.if ${.CURDIR:M*/lang/erlang}
WITHOUT_ODB
On Nov 20, 2007, at 11:37 AM, Sean McLaughlin wrote:
did you replace your system make with gmake? ports depends on the
BSD
make.
# which make
/usr/bin/make
what's the output of
/usr/bin/make --version
did you redefine the MAKE variable in your /etc/make.conf?
There are many ways to r
On Nov 20, 2007, at 2:05 AM, Sean McLaughlin wrote:
===> Configuring for arj-3.10.22_1
---> Installing the new version via the port
gmake: GNUmakefile: No such file or directory
gmake: *** No rule to make target `GNUmakefile'. Stop.
cd /usr/ports/archivers/arj/work/arj-3.10.22/doc && install
On Oct 24, 2007, at 6:26 PM, Aliya Harbouri wrote:
Or, maybe suggest a different route to getting it fixed?
submit your patch as a PR. wait for the maintainer time-out, then
ask it to be committed and it will be as per "the rules".
it seems all you need is another "else if" clause for DB
Can I get some love for http://www.freebsd.org/cgi/query-pr.cgi?
pr=117326 to get it committed? I've gotten several email requests
asking when this update will happen and I just keep pointing them to
the PR. Please at least get it in before the freeze next week. Thanks!
__
On Oct 11, 2007, at 10:37 AM, Clement Laforet wrote:
On Wed, Oct 10, 2007 at 12:28:23PM -0400, Vivek Khera wrote:
I have apache (2.0.59 from the port) configured on a 6.2/amd64 box
like this in my rc.conf:
It should be fixed with 2.0.61
clem
Thanks. I was also pointed to an old PR from
I have apache (2.0.59 from the port) configured on a 6.2/amd64 box
like this in my rc.conf:
apache2_be_enable="YES"
apache2_fe_enable="YES"
apache2ssl_fe_enable="YES"
apache2_be_configfile="/usr/local/etc/apache2/httpd-be.conf"
apache2_fe_configfile="/usr/local/etc/apache2/httpd-fe.conf"
apache
On Sep 24, 2007, at 6:48 PM, Edwin Groothuis wrote:
On Mon, Sep 24, 2007 at 11:11:02AM -0400, Vivek Khera wrote:
Thanks for submitting this new port, but I object to having a new
port created and assigned to me as the MAINTAINER. It just seems
wrong to do that.
You can't just drop
Hi... Sorry I've been out of the loop for a while.
Thanks for submitting this new port, but I object to having a new
port created and assigned to me as the MAINTAINER. It just seems
wrong to do that.
Furthermore, since this port replaces devel/p5-gearmand, it should
have either been repo
On Sep 12, 2007, at 3:40 PM, Kris Kennaway wrote:
But do they apply to a 6.x binary running on 7.0? i.e. are you
describing a 6.x kernel bug or a 6.x libthr bug?
Dunno which it is, but I don't have any 7.0 around here whatsoever.
So it is a 6.x binary running on 6.x.
_
On Sep 12, 2007, at 5:37 AM, Jiawei Ye wrote:
On 9/12/07, Jiawei Ye <[EMAIL PROTECTED]> wrote:
[/usr/local/diablo-jdk1.5.0/jre/bin/java]
libpthread.so.2 libthr.so
Changing this to libthr.so.2 fixes the problem. Sorry about the noise.
curious... on 6.1/6.2 I *must* use libpthread as the th
On Sep 10, 2007, at 1:15 PM, Pav Lucistnik wrote:
Create a port of that, the old FreeBSD versions depend on it to
install in
/usr/share/mk. I kind of don't like it, but it looks like it's only a
solution if it has to be in /usr/share/mk.
Doesn't solve anything. The files get installed _afte
On Aug 30, 2007, at 4:40 AM, Timur I. Bakeyev wrote:
Which threading libraries do you use? I remember having similar
problem with
libthr.so enabled in libmap.conf. As soon as I tried:
[java]
libpthread.so libpthread.so
libpthread.so.2 libpthread.so.2
All pr
On Aug 29, 2007, at 10:27 PM, Greg Lewis wrote:
FreeBSD 6.1/amd64 inside a jail.
Builds fine for me on 6.2/amd64 (but outside of a jail).
The hs_error*mumble*.log might provide some clues.
Timur figured it out: it was the threading library from libmap.conf.
Switching to libpthread allow
On Aug 30, 2007, at 4:40 AM, Timur I. Bakeyev wrote:
Which threading libraries do you use? I remember having similar
problem with
libthr.so enabled in libmap.conf. As soon as I tried:
[java]
libpthread.so libpthread.so
libpthread.so.2 libpthread.so.2
All pr
On Aug 29, 2007, at 4:44 PM, Greg Lewis wrote:
I asked over on the java mailing list, but was greeted with complete
silence. I know not much about java, but need jboss to run an
application we are planning to use.
What version of FreeBSD?
FreeBSD 6.1/amd64 inside a jail.
_
I'm trying to build the jboss4 port, but it keeps failing with Java
HotSpot compiler errors at differing locations. I'm using diablo-
jdk-1.5.0.07.01_6 with a freshly updated ports tree. The error I get
is this:
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Int
Can someone commit ports/115364 for me? It has been languishing for
20 days now, and people keep asking about the upgrade. Thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, sen
On Aug 27, 2007, at 10:16 AM, Stefan Lambrev wrote:
Hello,
I'm trying to make a small port, but want to ask what is the right
procedure,
if my port requires a certain user to be on the installed system?
Do I have to use pkg-install/pkg-deinstall for this?
P.S. Please CC me as I'm not subs
On Aug 15, 2007, at 1:48 PM, Doug Barton wrote:
One question though, are ALL of those modules truly needed for
build AND run? If yes, no problem, but I hate to see BUILD_DEPENDS
== RUN_DEPENDS as a default if it hasn't been thought through. (Not
saying that's the case here, that's why I'm
Can some kind ports committer give some tender loving care and commit
the upgrade to RT for me? Thanks!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.MailerMailer, LLC Rockville, MD
http://www.MailerMailer.com
en it needs updating.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.MailerMailer, LLC Rockville, MD
http://www.MailerMailer.com/ +1-301-869-4449 x806
___
freebsd-
On Jul 17, 2007, at 9:54 PM, Peter Beckman wrote:
Is there a way, using portupgrade, to upgrade bsdpan-* to p5-* and
use the
p5-* package, so that at the end of the process, I'm left with
only p5-*
packages and not bsdpan-* packages?
The -o option to portupgrade might do it, but it won
On Jun 13, 2007, at 3:36 AM, Alexander Leidinger wrote:
First there where no OPTIONS, then OPTIONS was introduced. If you
feel annoyed by those ports which are not converted yet to OPTIONS
(because nobody felt annoyed enough to convert them), feel free to
submit patches for them.
persona
On May 27, 2007, at 12:13 PM, [EMAIL PROTECTED] wrote:
Here is the error:
Updating the ports index ... Generating INDEX.tmp - please wait..===>
arabic/ae_fonts_mono failed *** Error code 1
===> accessibility/at-poke failed
*** Error code 1
2 errors
go to the directory for that port and type
On Apr 25, 2007, at 1:22 PM, Bill Moran wrote:
My thought is to make /usr/ports/private (or similar) and teach cvsup
not to blow it away. Then I just need to make sure that portupgrade
and other tools see it.
Does anyone have a HOWTO or list of steps to get this going? I know
this has been d
On Apr 9, 2007, at 5:46 AM, Palle Girgensohn wrote:
About the two "strategies" you present; autovacuum will probably
need some tweaking for most applications, since it will not perform
vacuums unless a certain percentage of the tuples are changed.
Hence, usually I use a combination of auto
On Mar 27, 2007, at 4:11 AM, Anton Berezin wrote:
Hmm. Presumably any method you use except when a module is in the
ports
collection would not work with portupgrade and friends, for a suitable
definition of "work".
If you want portupgrade and other methods to do the upgrades for
you, yo
On Mar 8, 2007, at 9:31 PM, Nicholas Honywood wrote:
After successful compile and "make install"
/usr/local/sbin/httpd -M
shows all the unwanted default modules build and installed regardless
of everything after the "make" in my command line.
be sure to pass all your flags to the "make inst
On Feb 13, 2007, at 2:00 PM, Kris Kennaway wrote:
On Tue, Feb 13, 2007 at 04:37:00PM +0100, Palle Girgensohn wrote:
Hi!
As the maintainer of the PostgreSQL ports, I'm planning a move to
set the
8.1.x branch as the default version for FreeBSD. Now it is 7.4, which
starts to get a bit rusty.
On Jan 31, 2007, at 3:48 PM, Paul Chvostek wrote:
you just do it manually, perhaps using portdowngrade on each host, or
installing binary packages built on one host?
we build packages on the QA cluster and install them everywhere.
Next, how are people dealing with portaudit info for groups
On Jan 14, 2007, at 11:22 PM, Jayel Villamin wrote:
I'm not sure if packages are covered by "ports" so apologies in
advance if I made a mistake.
===
I installed php5 via packages: pkg_add -r php5. The machine is
currently running 6-stable (or 6.2-PRERELEASE according to unam
On Dec 11, 2006, at 7:09 PM, Jun Kuriyama wrote:
Anyway, this way maybe old-porters thinking. I liked to use
"/" directory name (without version number).
Using version number in ports directory is very exceptional event for
keeping old ports (like "emacs", "emacs19", "emacs20"). I thought
thi
People should avoid using the 1.2.0 and 1.2.1 releases unless they
really know what they're doing and can fix the problems that may
arise.
If you want we can...
- Backout the changes to 1.1.5
- Put a FORBIDDEN in the makefile so people will know about the
issues.
Nah. It works for new in
On Dec 11, 2006, at 6:41 PM, Mark Linimon wrote:
Well, this looks to have been a combination of two human errors (on
that
particular PR), which the code really doesn't know how to deal
with. But
after looking at it, I'm not too sure what we could have done
differently.
Human error I can
On Dec 11, 2006, at 12:47 PM, Martin Wilke wrote:
For this update of 1.2.0 gives a pr show here
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/105575 here is my
mistake thats commit is after 7 days not 14 days. This is my mistake
right. After this commit, I received a private email with a bu
On Dec 11, 2006, at 12:47 PM, Martin Wilke wrote:
On 23 Nov 2006, an update was issued to upgrade the 1.1.5 version to
1.2.0 which had known errors in it which cause data loss. Somehow
it was applied. A few days later a manual patch was added to work
around that. The initial update indicate
It seems that the change log on freshports for the databases/slony1
port shows that someone somewhere is confused as to who's the
maintainer of the port. The Makefile clearly shows it is still me.
On 23 Nov 2006, an update was issued to upgrade the 1.1.5 version to
1.2.0 which had known err
On Nov 29, 2006, at 3:46 AM, Sergey Matveychuk wrote:
I suppose the bug is that I expected portupgrade -Rr to recompute the
dependency lists of the upstream ports to take into account any
changing
dependencies of the updated port.
portupgrade -Rr do not recompute dependencies. It do port
On Nov 28, 2006, at 1:20 PM, Doug Barton wrote:
I suppose the bug is that I expected portupgrade -Rr to recompute
the dependency lists of the upstream ports to take into account
any changing dependencies of the updated port.
Do other port manager utilities take this type of change into
acc
are
accurate on the complex ports like RT.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.MailerMailer, LLC Rockville, MD
http://www.MailerMailer.com/ +1-301-869-4449 x806
On Nov 22, 2006, at 4:45 AM, Stefan Lambrev wrote:
Hello,
Why aaccli is marked only for arch i386 ? :)
It's a binary package build for i386, but it work perfect on amd64.
Is there any other reason for this?
I've asked this before to a resounding silence.
As long as you have COMPAT for FreeB
On Nov 13, 2006, at 5:25 PM, Bill Moran wrote:
In response to Harlan Stenn <[EMAIL PROTECTED]>:
Will this "keep" across a "make update", or do I need to re-do
it every
time I update /usr/ports?
I'm not familiar with using "make update" and I don't see any
info on
it in man ports.
I
On Nov 3, 2006, at 3:30 PM, Charles Sprickman wrote:
Is there some mechanism that I'm missing to deal with a local
category? I've been googling without much luck, and I didn't see
this addressed in the porter's handbook.
Check the June 8 archives for this mailing list, for my message wit
On Oct 28, 2006, at 2:39 AM, Andreas Klemm wrote:
At the moment I only found the variable WITHOUT_X11.
But its only for ports, that can be built optionally with and without
X11 support. It doesn't hinder directly to built x11 stuff using ports
collection.
I also find that you need to set WIT
On Oct 24, 2006, at 7:09 PM, Brian A. Seklecki wrote:
You should try to work closely with the FreeBSD port maintainer for
sysutils/syslog-ng to integrate 2.x into a Port. Unless there is a
liscencing restriction I don't know preventing a enw sysutils/
syslog-ng2/ port, we're still at 1.6.1
On Oct 5, 2006, at 10:34 PM, Jo Rhett wrote:
So it appears that installing perl packages from outside of ports
nicely
creates bsdpan packages in the pkg tree. However, I'm having
trouble with
upgrades duplicating the packages, so I was going to do into this and
figure out what's missing.
On Aug 21, 2006, at 6:57 PM, Ian A. Tegebo wrote:
We already use Apache22 and mod_perl2 for a number of applications so
we'd like to keep it that way and not have to support apache13 with
fastcgi.
fastcgi works just fine with apache 2 also.
personally, I use rt with the fastcgi option. much easier to get it
running that way, and RT doesn't need any of the advanced features of
mod_perl so it seems overkill.
but anyhow your error seems related to p5-Log-Dispatch not rt36.
On Aug 21, 2006, at 4:31 PM, Ian A. Tegebo wrote:
Does
On Aug 15, 2006, at 10:52 AM, David Sledge wrote:
I installed rails using gems, I have not seen any problems with it
yet.
I personally don't use ruby, but a similar situation exists with perl
and the CPAN archives. I used to install all modules via CPAN
directly, but in the long run it
On Jul 13, 2006, at 4:51 PM, Benjamin Lutz wrote:
On Thursday 13 July 2006 04:29, lveax wrote:
vmware server 1.0 was released and free for download,there are
windows
and linux version,would anyone bring the linux version to freebsd
ports?
Unlikely to happen, since VMWare uses a linux kerne
On Jul 6, 2006, at 11:24 AM, Brooks Davis wrote:
Actually I think it's confused by the fact that the package name is
"diablo-jdk" and the version is "freebsd6.i386.1.5.0.07.00". That's
just plain bogus.
So who is at fault? The ports infrastructure or the FreeBSD
foundation?
I don't know.
On Jun 26, 2006, at 2:26 PM, Shaun Amott wrote:
Try ${APACHEMODDIR} :-)
I love it how once you know it is there it becomes obvious that it
was always there...
Thanks!
On Jun 25, 2006, at 1:57 PM, Sevan / Venture37 wrote:
I tried to upgrade the fresh 3.4.5 install I did last week using your
port & it didnt work. It seems that the UPGRADE_RT34 build option
upgrades RT 3.5.1.
Hmmm.. the upgrade is supposed to apply any "patches" between your
version and the
How does one handle the dependency list in the port for a port which
needs mod_perl, but doesn't care if it is in apache 2.0 or 2.2.
In apache 2.2 modperl is installed in /usr/local/libexec/apache22/
mod_perl.so, and in apache 2.0, /usr/local/libexec/apache2/mod_perl.so.
I don't see in bsd.a
On Jun 23, 2006, at 6:56 PM, Erwin Lansing wrote:
patch, I'd say that this rule goes for the rt34 to rt36 move as well.
Unless the new source is completely unrelated to the old one, a
repocopy
is the way to go.
Yes, 3.6.0 is the evolution of 3.4 line, but is a non-trivial upgrade
and peo
I've prepared the port for RT 3.6.0 for those interested. It is
sitting at
http://vivek.khera.org/scratch/rt36port.tar.bz2
download it and extract into /usr/ports/www and then install as usual.
I'd like some folks to test it out before committing it, as I have
really only tested building w
85 matches
Mail list logo
