Re: Question About Ports Update Cycle

[Matthew Seaman]

Tim Daneliuk wrote:

Is there some regular interval at which new ports are processed by the
FreeBSD team?  I submitted a port (for a very minor utility) 3/20/2008
but it is still not in the tree.  I'm not complaining in the slightest -
the folks who do this work are volunteering their time, and I get/respect
that.  I'm just curious if there is some window you have to hit to get
stuff in.

Just curious, not beefin',


There's no particular schedule for bringing in new ports -- it's all
just part of the same flow of updates, patches etc. etc.

If your submission is still languishing unattended after about 3 weeks,
then it has probably been overlooked, and it would not be amiss to send
a follow-up asking if there's a problem.  Most ports PRs are dealt with 
considerably faster than that, although the initial import of a new port

does take longer than a routine update to an existing port.

One important general point is that any one sending in PRs should supply
a working e-mail address in what they send -- if a port maintainer needs
to ask a question or for some other form of feedback, and their e-mail to
the PR originator bounces, then that PR is simply not going to get
processed.  


Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Question About Ports Update Cycle

[Tim Daneliuk]

Is there some regular interval at which new ports are processed by the
FreeBSD team?  I submitted a port (for a very minor utility) 3/20/2008
but it is still not in the tree.  I'm not complaining in the slightest -
the folks who do this work are volunteering their time, and I get/respect
that.  I'm just curious if there is some window you have to hit to get
stuff in.

Just curious, not beefin',

Tim Daneliuk [EMAIL PROTECTED]
PGP Key: http://www.tundraware.com/PGP/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

question about ports: php5-extensions

[James liu]

FB 6i first setup freetds in /usr/local/freetds
and use its tsql to test connect ms sql server, it is ok.

setup php5-extensions,,and click mssql(option)

i find it use another freetds,,,but not show me error information.  setup is
complete.

i can find mssql support with phpinfo.

so i use


and it show me
Unable to connect: 192.168.7.112

i use winxp and tsql(freetds test tool)to test connection...they all ok.

i read php handbook and googleall show me setup with
-with-mssql=/usr/local/freetds

but php5-extensions seems to do it(just click checked mssql)

am i right? and how can i fix it ?

anyone know?



--
regards
jl
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Question about ports builds

[Chuck Swiger]

Charlie Sorsby wrote:

Charlie Sorsby wrote:
[ ... ]

PS It would be really helpful if each port/package at freebsd.org
had an indication whether it requires the latest and greatest
version of freeBSD.  Put another way, it would be nice to know the
oldest version of freeBSD it will work with.  Perhaps that could be
included in the "Requires" list on the page for the port/package.
The people maintaining the ports attempt to support them on all of the active 
versions of FreeBSD, which means 4.10 or 4.11, 5.3 and later, 6.0 and later, 
and -CURRENT (what will become 7.0).


I find it hard to believe that 4.10 and 4.11 are even considered
"active versions"; I can't find anything about either at the web
site.  Try putting 4.11 into the search box on the freebsd.org home
page.


4.11 is a legacy version and will be supported through Jan 31, 2007:

http://www.freebsd.org/security/
http://www.freebsd.org/releng/index.html

4.x is no longer recommended for a new installation.


Anyway, I'm afraid that I haven't had much luck with new versions
of ports relative to those distributed on the 4.11 CDROM and, in
fact, have had problems trying to install some of those.  When I
installed 4.11, I did have sysinstall install /usr/ports.  Frequently
trying even to install from that directory tree fails.


You need to update your ports tree.  Read the fine documentation:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html


My experience has been that trying to install ports on 4.11
frequently produces complaints that it can't find some *4.11*
directory at freeBSD.org.


If your ports tree comes from the original CD, you're trying to fetch old 
versions of the packages which have been updated since.


Support for 4.x is going away soon, 


Are you sure it isn't already gone?


Yes.


however, and it will become more common for new ports to not
work on 4.x as  time passes.


With each successive (major) version of freeBSD, it becomes less
and less like BSD and more and more "invented here."  I suggest
that the "BSD" be dropped from the name of the operating system
currently being produced.


You're welcome to your opinion, even if it smells like flamebait to me.

For those ports that do not work with an older version like 4.x because of 
features added to more recent versions of the operating system, ports usually 
will indicate this in the Makefile.


Are you saying that the only way to tell is to fetch the new
version of the port, unpack it, and read the Makefile?


Nope.  There's cvsweb access and sites like freshports.org...


I just looked in the Makefile for .../graphics/gphoto2 that I just
fetched from freeBSD.org -- specifically from:

http://www.freebsd.org/cgi/ports.cgi?query=gphoto2&stype=all)

I could find nothing about an OS version but it may just be that I
don't know specifically what to look for.

In any event, build failed:

Thursday,  6 Jul, 2006 -- 10:56:22 MDT
=> gphoto2-2.2.0.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch from 
http://heanet.dl.sourceforge.net/sourceforge/gphoto/.
gphoto2-2.2.0.tar.bz2  530 kB   25 kBps
===>  Extracting for gphoto2-2.2.0
=> Checksum OK for gphoto2-2.2.0.tar.bz2.
===>  Patching for gphoto2-2.2.0
-e: not found
*** Error code 127

Stop in /home/crs/Incoming/Ports/gphoto2.


Supporting sed -e/REINPLACE_CMD happened somewhere around 4.8 or 4.9, so your 
version of the port Makefiles apparently predate this.


Your ports infrastructure is rather non-standard and being so far out-of-date, 
isn't likely to work properly without being updated per the directions above, 
although you could always go your own way and compile the software for yourself...


[ ... ]

Charlie

PS Having used "real" BSD (4.[123], SunOS 4.1, etc), I wouldn't even
buy a PC until FreeBSD became available.  Now I find that each
successive release of free"BSD" is less and less BSD and more and
more something else.  That's why I'm still using 4.11 (and probably
will continue to do).  I think the powers-that-be at freebsd.org
should seriously consider dropping the "BSD" part of the name.


Yeah, you said that above, too.  Feel free to use another operating system if 
you find something that suits you better


--
-Chuck
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Newbie question about ports.

[RW]

On Friday 24 June 2005 19:36, Alex Zbyslaw wrote:
> Sam Ip wrote:
> >I'm trying out FreeBSD for the first time for use at work.  However,
> >there is a corporate firewall and hence ftp traffic doesn't get
> >through. I can access http sites.  So if a selling point of FreeBSD is
> >its ports collection
> >
> >1.  Can you do a CVSup to update your ports via http?
> >
> >2.  Can you install ports via http?
>
> Cvsup does not support http, but neither does it use ftp (see man cvsup,
> especially the -p and -P options).  It requires that a single port be
> openable through your firewall (default 5999).  There is an alternative,
> which I have never used, called CTM (see handbook).

See also sysutils/portsnap which uses http
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Newbie question about ports.

[Andrew L. Gould]

On Friday 24 June 2005 01:01 pm, Sam Ip wrote:
> Hi,
>
> I'm trying out FreeBSD for the first time for use at work.  However,
> there is a corporate firewall and hence ftp traffic doesn't get
> through. I can access http sites.  So if a selling point of FreeBSD
> is its ports collection
>
> 1.  Can you do a CVSup to update your ports via http?
>
> 2.  Can you install ports via http?
>
> Thanks!
>
> Sam

Welcome to FreeBSD!  I hope it's a good experience; but be warned that 
it may be addictive.

I **think** the answer to both questions is "no" since the files you 
need are on ftp servers.

One (fairly expensive) option for you is to order a DVD of  binary 
packages for the release that you installed.  The 2 sources of FreeBSD 
DVD's  that I'm aware of are www.freebsdmall.com and bsdmall.com.

Best of luck,

Andrew Gould
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Newbie question about ports.

[Alex Zbyslaw]

Sam Ip wrote:


I'm trying out FreeBSD for the first time for use at work.  However,
there is a corporate firewall and hence ftp traffic doesn't get
through. I can access http sites.  So if a selling point of FreeBSD is
its ports collection

1.  Can you do a CVSup to update your ports via http? 


2.  Can you install ports via http?
 

Cvsup does not support http, but neither does it use ftp (see man cvsup, 
especially the -p and -P options).  It requires that a single port be 
openable through your firewall (default 5999).  There is an alternative, 
which I have never used, called CTM (see handbook).


Ftp is required to fetch the source code for ports, but this happens 
when you try and build a port and has nothing to do with cvsup.  The ftp 
connection used to fetch the sources will be a "passive" connection 
which is firewall friendly.  There is no reason, beyond pure paranoia or 
obscene mistrust of employees, for a firewall to block passive-style ftp 
connections.  If I were you, I would ask whoever is in charge of your 
corporate firewall if they do allow passive ftp, and  if they don't, 
then ask for an explanation why not.  If your FreeBSD requirement is 
business related, then they should be helping you get these basic 
services working.


The firewall can easily limit ftp and cvsup connections to be from a 
specified IP address, and to a specified IP address.  Security 
implications: none, since far more dangerous things can be carried in to 
the business on a CD.


*If* (and I have no idea about this) there is a server which has the 
port sources available via HTTP, then you could download them yourself 
either with a web browser or something like lwp-download (part of the 
p5-libwww-5.803 perl package, and quite possibly part of the standard 
perl port).  Every time a port fails to fetch a package via ftp, you 
would have to download it by hand.


The ports collection is *one* selling point for FreeBSD (stability, 
documentation, and just being better than anything else :-) are some 
others).  However, there is no way that you can expect anyone to waste 
their time to work around what can only be described as demented 
security restrictions.


You might be better off looking for a server which can supply you 
packages via HTTP.  Packages are pre-built ports comparable to Linux 
RPMs.  Just like Linux RPMs you get no choice about any configurations 
options which the port provides, and are stuck with whatever the package 
creator used.  That's one reason why the ports are so nice.  See the 
pkg_add manual page and the handbook section on ports and packages.


Just my 0.02,

--Alex






___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Newbie question about ports.

[Sam Ip]

Hi,

I'm trying out FreeBSD for the first time for use at work.  However,
there is a corporate firewall and hence ftp traffic doesn't get
through. I can access http sites.  So if a selling point of FreeBSD is
its ports collection

1.  Can you do a CVSup to update your ports via http? 

2.  Can you install ports via http?

Thanks!

Sam
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Question about Ports and Packages

[Lowell Gilbert]

Tom Moyer <[EMAIL PROTECTED]> writes:

> I'm using FreeBSD 5-STABLE installed from 5.4-RC1 and then cvsup'd to
> 5-STABLE on Friday.
> 
> Maybe I'm just doing something wrong, but I noticed that when I did
> pkgdb -F or portsdb -Uu, it seemed to complain about build
> dependancies missing for packages that I installed from packages.  I
> assumed that it would catch this and not prompt me to fix stale
> dependacies like that.

I've never had it warn me about build dependencies.  I don't think the
ports database even tracks them.  Are you sure those aren't runtime
dependencies?

> Along those same lines:  I deleted a build dependancy before I decided
> to skip them, is there any way to fix that automatically?

Sorry; I don't understand the question.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Question about Ports and Packages

[Tom Moyer]

I'm using FreeBSD 5-STABLE installed from 5.4-RC1 and then cvsup'd to
5-STABLE on Friday.

Maybe I'm just doing something wrong, but I noticed that when I did
pkgdb -F or portsdb -Uu, it seemed to complain about build
dependancies missing for packages that I installed from packages.  I
assumed that it would catch this and not prompt me to fix stale
dependacies like that.

Along those same lines:  I deleted a build dependancy before I decided
to skip them, is there any way to fix that automatically?

Thanks,
Tom
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Dumb question about ports/packages

[Lowell Gilbert]

Ian Moore writes:

> On Fri, 11 Feb 2005 17:50, Matt Rechkemmer wrote:

> > Final question :-), is there anyway to determine if a base package is out
> > of date? Or is just wise to leave the base alone and upgrade when a new
> > release comes along.
> 
> You should at least update your system when security vulnerabilities occur in 
> the base system. To minimise upgrades, follow the security  branch for your 
> release - this only has security fixes, not new features. See the handbook 
> for details. Subscribe to the Security Notifications list to get notification 
> of base system vunerabilities.

The current policy for the release branches is that they are not
"security" branches, they are "errata" branches.  The practical upshot
of this is that some particularly serious non-security problems do get
fixed on them.

To follow up a bit farther on the original poster's question: if you
don't know about a new version of software in the base system, and
you're not having problems with it, you don't need to update.  This
doesn't apply to security problems, of course, which is why following
the security advisories is essential.  FreeBSD is designed to work
well as an entire OS, so very few people need to update the base
system piecemeal.  [This is why FreeBSD is very conservative about
adding anything new to the base system.]

Be well..
-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Dumb question about ports/packages

[Ian Moore]

On Fri, 11 Feb 2005 17:50, Matt Rechkemmer wrote:
> On Tue, Feb 08, 2005 at 09:45:07AM -0500, Lowell Gilbert wrote:
> These are probably RTFM questions, but I didn't seem to find a mention of
> the base system packages in the UPGRADING document.  So how would one
> update a base package, check it out of CVS and just compile/install like
> normal?

There are 2 UPDATING files - /usr/ports/UPDATING for the ports collection 
& /usr/src/UPDATING for the base system.

> Should upgrading the entire system become a necessity (say 4.10 to 4.11),
> would a reboot be *absolutely* necessary?
Yes, if you update your kernel, you can't load it except by re-booting.
The 'correct' and safest way to update is to do the update, as the handbook 
says, involves doing

# mergemaster -p
# make installworld
# mergemaster
# reboot
in single user mode.

>
> Final question :-), is there anyway to determine if a base package is out
> of date? Or is just wise to leave the base alone and upgrade when a new
> release comes along.

You should at least update your system when security vulnerabilities occur in 
the base system. To minimise upgrades, follow the security  branch for your 
release - this only has security fixes, not new features. See the handbook 
for details. Subscribe to the Security Notifications list to get notification 
of base system vunerabilities.

Cheers,
-- 
Ian

GPG Key: http://home.swiftdsl.com.au/~imoore/no-spam.asc


pgpCYVlBgi3rG.pgp
Description: PGP signature

Re: Dumb question about ports/packages

[Matt Rechkemmer]

On Tue, Feb 08, 2005 at 09:45:07AM -0500, Lowell Gilbert wrote:
> 
> Um, no, as the original poster pointed out, ssh is part of the base
> system, and normally you don't need the port.  
> 
> Upgrading the base system *is* the best approach.  It *doesn't*
> normally require updating to the latest release; 4.10, for example, is
> still a supported branch, and will be for (at least) another year or
> so.  Updating to the latest of the 4.10 branch will do fine for this
> kind of problem.

These are probably RTFM questions, but I didn't seem to find a mention of the
base system packages in the UPGRADING document.  So how would one update a
base package, check it out of CVS and just compile/install like normal?

Should upgrading the entire system become a necessity (say 4.10 to 4.11),
would a reboot be *absolutely* necessary? 

Final question :-), is there anyway to determine if a base package is out of
date? Or is just wise to leave the base alone and upgrade when a new release
comes along.

Many thanks,

--
Matt Rechkemmer
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Dumb question about ports/packages

[Lowell Gilbert]

Olivier Nicole <[EMAIL PROTECTED]> writes:

> > How would I upgrade just one package part of the core like that? Or multiple
> > ones for that matter.  Can you use the ports/packages system? Or do you have
> > to do an entire system upgrade (i.e. 4.10 to 4.11).  
> 
> I'd say, given that ssh is part of the ports
> (/usr/ports/security/ssh), you could ust upgrade that port and install
> that port.
> 
> I'd cvsup ports/security
> 
> then make && make install for ssh

Um, no, as the original poster pointed out, ssh is part of the base
system, and normally you don't need the port.  

Upgrading the base system *is* the best approach.  It *doesn't*
normally require updating to the latest release; 4.10, for example, is
still a supported branch, and will be for (at least) another year or
so.  Updating to the latest of the 4.10 branch will do fine for this
kind of problem.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Dumb question about ports/packages

[Lowell Gilbert]

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
http://be-well.ilk.org/~lowell/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Dumb question about ports/packages

[Olivier Nicole]

> How would I upgrade just one package part of the core like that? Or multiple
> ones for that matter.  Can you use the ports/packages system? Or do you have
> to do an entire system upgrade (i.e. 4.10 to 4.11).  

I'd say, given that ssh is part of the ports
(/usr/ports/security/ssh), you could ust upgrade that port and install
that port.

I'd cvsup ports/security

then make && make install for ssh

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Dumb question about ports/packages

[gabriel]

a patch would be issued for the source.


On Tue, 8 Feb 2005 01:57:48 -0700, Matt Rechkemmer
<[EMAIL PROTECTED]> wrote:
> This is somewhat of a dumb question, but I'm a bit confused about the
> differences between ports, packages and what is currently on the system.
> Let's [hypothetically] say I have a FreeBSD 5.3 system.  I use the ports
> system on things I want to compile and packages when I'm lazy :-).
> 
> I keep track of my ports 'n' packages with portupgrade(1).  Now here's the
> scenario (fake, mind you).  Let's say SSHD which is part of the core
> distribution from my limited understanding develops a root hole, or some other
> nasty exploit.
> 
> How would I upgrade just one package part of the core like that? Or multiple
> ones for that matter.  Can you use the ports/packages system? Or do you have
> to do an entire system upgrade (i.e. 4.10 to 4.11).
> 
> Any help is greatly appreciated!
> 
> Matt Rechkemmer
> [EMAIL PROTECTED]
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> 


-- 
gabriel,

Member of:
FreeBSD-Announce
FreeBSD-Hardware
FreeBSD-Multimedia
FreeBSD-questions
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Dumb question about ports/packages

[Matt Rechkemmer]

This is somewhat of a dumb question, but I'm a bit confused about the
differences between ports, packages and what is currently on the system.
Let's [hypothetically] say I have a FreeBSD 5.3 system.  I use the ports
system on things I want to compile and packages when I'm lazy :-).

I keep track of my ports 'n' packages with portupgrade(1).  Now here's the
scenario (fake, mind you).  Let's say SSHD which is part of the core
distribution from my limited understanding develops a root hole, or some other
nasty exploit.

How would I upgrade just one package part of the core like that? Or multiple
ones for that matter.  Can you use the ports/packages system? Or do you have
to do an entire system upgrade (i.e. 4.10 to 4.11).  

Any help is greatly appreciated!

Matt Rechkemmer
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Question about ports

[whitevamp]

when u upgrade perl to a newer ver useing the ports tree its quit simple .
at the end of it installing it tell you that if u whant to use that version
u need to use this command onley once though use.perl port and then u also
need to read README in the bas dir of the ports tree IE: /usr/ports/UPDATING
in there it talks about getting all the perl progs switched over to the
newer ver of perl and thats it..  or at least that worked 4 me
PS: you might whant to look at /usr/ports/UPDATING before you go and install
perl ..thats a good file to read after u cvsup your tree
- Original Message - 
From: "Nikolas Britton" <[EMAIL PROTECTED]>
To: "Pierre LeBlanc" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, October 06, 2004 5:16 PM
Subject: Re: Question about ports


> Pierre LeBlanc wrote:
>
> >Hello,
> >
> >I'm new to the port collection and updating ports with CVSup but I
managed to
> >update the ports of my FreeBSD 4.10 system using CVSup.
> >
> >Now, I want to upgrade Perl to version 5.6 and I notice there is a perl5
port
> >in the list I`ve seen on:
> >
> >ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.10-release/
> >
> >But this port is not on my system and to understand how to get perl5 in
my
> >port collection, I searched on the Internet for several hours without
success.
> >
> >Can you refer me a specific page or a chapter in the FreeBSD manual that
> >describe how to do it?
> >
> Well see... the thing is is that perl is part of the base system in 4.x
> (and quasi-base in 5.x), FreeBSD is dependent on it. I like to know this
> question too, what are the pros/cons and procedure for updating perl to
> ether 5.6.x or 5.8.x
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Question about ports

[Nikolas Britton]

Pierre LeBlanc wrote:
Hello,
I'm new to the port collection and updating ports with CVSup but I managed to 
update the ports of my FreeBSD 4.10 system using CVSup.

Now, I want to upgrade Perl to version 5.6 and I notice there is a perl5 port 
in the list I`ve seen on:

ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.10-release/
But this port is not on my system and to understand how to get perl5 in my 
port collection, I searched on the Internet for several hours without success.

Can you refer me a specific page or a chapter in the FreeBSD manual that 
describe how to do it?

Well see... the thing is is that perl is part of the base system in 4.x 
(and quasi-base in 5.x), FreeBSD is dependent on it. I like to know this 
question too, what are the pros/cons and procedure for updating perl to 
ether 5.6.x or 5.8.x

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Question about ports... [postnuke]

[Pete Renshaw]

Did you try
make install FORCE_PKG_REGISTER=yes clean

See
http://www.freebsd.org/cgi/man.cgi?query=ports&apropos=0&sektion=0&manpath=FreeBSD+5.1-RELEASE+and+Ports&format=html

Many people don't know to use the "=yes" for FORCE_PKG_REGISTER.

After you get Postnuke installed you may have to make these changes below.

 "Using FreeBSD 5.1 and PHP 4.3 I had to delete the " from: setlocale
("LC_TIME", "locale"); To make it look like: setlocale (LC_TIME,
"en_US.ISO_8859-1"); and also replace setlocale (try "man setlocale" info)
>From mainfile.php line 565"

Pete
http://www.soupro.org/dim


On Thu, 11 Dec 2003 14:03:04 -0500, C. Ulrich wrote
> On Wed, 2003-12-10 at 12:04, Payne wrote:
> > Hi,
> > 
> > I am want to install postnuke but when-ever I go to do make under 
> > /usr/port/www/postnuke, it wants to install mod_php4 again, I don't want 
> > to have to reinstall ports everytime I add something new.
> > 
> > Thanks,
> > 
> > Payne

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Question about ports... [postnuke]

[HOLLOW, CHRISTOPHER]

Given PHPNuke's security track record, I would say that this is sound 
advice.  I would suggest going from the latest source as well.

Chris

Matt Staroscik wrote:

I am want to install postnuke but when-ever I go to do make under
/usr/port/www/postnuke, it wants to install mod_php4 again, I don't want
to have to reinstall ports everytime I add something new.
 

I recently installed PHPNuke and have some observations that might be
relevant to your situation.
1. The version in ports may be behind what is on the project web site.

2. Installing a PHP app from a tarfile is pretty easy, so if ports isn't
cooperating, go to the source. You'll probably just need to edit the
config file with your SQL login info and the user/group that the web
server runs as (probably nobody/nogroup).
Good luck!

--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
 

--
Christopher Hollow - Technical Consultant
Infrastructure & Technology Support
Toronto, ON


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Question about ports... [postnuke]

[Matt Staroscik]

>> I am want to install postnuke but when-ever I go to do make under
>> /usr/port/www/postnuke, it wants to install mod_php4 again, I don't want
>> to have to reinstall ports everytime I add something new.

I recently installed PHPNuke and have some observations that might be
relevant to your situation.

1. The version in ports may be behind what is on the project web site.

2. Installing a PHP app from a tarfile is pretty easy, so if ports isn't
cooperating, go to the source. You'll probably just need to edit the
config file with your SQL login info and the user/group that the web
server runs as (probably nobody/nogroup).

Good luck!

--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Question about ports...

[C. Ulrich]

On Wed, 2003-12-10 at 12:04, Payne wrote:
> Hi,
> 
> I am want to install postnuke but when-ever I go to do make under 
> /usr/port/www/postnuke, it wants to install mod_php4 again, I don't want 
> to have to reinstall ports everytime I add something new.
> 
> Thanks,
> 
> Payne

Does postnuke require a newer or different version of mod_php4 than you
have currently installed? Unless your mod_php4 installation is in some
way customized, there should be little harm in letting ports do whatever
it wants to do.

(Ports, I've found, works best when it gets its own way. :P)

Charles Ulrich
-- 
http://bityard.net

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Question about ports...

[Payne]

Hi,

I am want to install postnuke but when-ever I go to do make under 
/usr/port/www/postnuke, it wants to install mod_php4 again, I don't want 
to have to reinstall ports everytime I add something new.

Thanks,

Payne

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: question about ports

[Jens Rehsack]

Antoine Jacoutot wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 15 July 2003 12:51, Jens Rehsack wrote:

This usually went this way, even if I don't want to prevent you from
asking the ports maintainer to accept/commit your patch. Usually you
create the patch against mgetty, send this patch to the mgetty
author(s). If they accept your patch and it's included into the next
The mgetty authors are the one who told me to try this patch. I don't 
think they'll include it in their next release since it is a "specific 
modem" issue.
I think they do when the patch is approved. This patch is mgetty
specific, not FreeBSD specific.
So do as I described and send them your results.

Nope, only directories and files which were in the cvs tree before
and became deleted are deleted at your machine, too, when you've
specified '*default delete' in your cvsupfile.
Hey, this is great :)
That's FreeBSD :-)

Best,
Jens
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: question about ports

[Antoine Jacoutot]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 15 July 2003 12:51, Jens Rehsack wrote:
> This usually went this way, even if I don't want to prevent you from
> asking the ports maintainer to accept/commit your patch. Usually you
> create the patch against mgetty, send this patch to the mgetty
> author(s). If they accept your patch and it's included into the next

The mgetty authors are the one who told me to try this patch. I don't 
think they'll include it in their next release since it is a "specific 
modem" issue.

> Nope, only directories and files which were in the cvs tree before
> and became deleted are deleted at your machine, too, when you've
> specified '*default delete' in your cvsupfile.

Hey, this is great :)

> No thanks, therefore is the questions@ list. AFAIK php has such a
> one, too, hm?

yep...

Antoine
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/E92mY3Hnhkr+5cQRAtEfAJ0ZBjZkEy6fVmRt996tlpVhBGkJPACfRcFO
1AI6izGEjB5ZDcEBqRk97vU=
=XCui
-END PGP SIGNATURE-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: question about ports

[Jens Rehsack]

Antoine Jacoutot wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 15 July 2003 12:25, you wrote:
[...]

In fact I wanted to try adding an option in mgetty, like:
"if WITH_USR=yes, then patch the mgetty source"
This usually went this way, even if I don't want to prevent you from
asking the ports maintainer to accept/commit your patch. Usually you
create the patch against mgetty, send this patch to the mgetty
author(s). If they accept your patch and it's included into the next
release, the port may be enhanced with a flag 'WITH_USR' which enables
eg. the CONFIGURATION_ARGS '--with-usr'.
You can place the patch for mgetty into the files/ directory in the
port location, the name of the patchfile must start with patch- to be
applied automatically. You should create the patch in that way you will
submit it to the mgetty author(s), so you can prove it's full working
and don't blame yourself with sending broken code.
I'll have alook at the porters handbook.
It's a good start :-)

Yes, on you own machine you can have each directory you want. If you
want to change something in the ports structure, you should ask the
PortManagers at [EMAIL PROTECTED] and substantiate your
requirement.
OK, but if I cvsup, won't my directory be erased ?
Nope, only directories and files which were in the cvs tree before and
became deleted are deleted at your machine, too, when you've specified
'*default delete' in your cvsupfile.
Hope it helps a little bit.
I does, thanks a lot :)
No thanks, therefore is the questions@ list. AFAIK php has such a one, 
too, hm?

Best,
Jens
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: question about ports

[Antoine Jacoutot]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday 15 July 2003 12:25, you wrote:
> Just to give you an example.
> a) If I want to have the FreeBSD php4-port is able to work with
> thttpd, I have to update the lang/php4/Makefile and
> lang/php4/bsd.php.mk to recognize a new flag for the port and
> choosing it's dependencies right. This patch I will send to the
> FreeBSD Gnats database and to the ports maintainer using send-pr(1).
> b) If I want php - just as example - be able to use libpopt (option
> parsing library, better than getopt()), I have to patch php and
> please the php developers to include the patch into the next
> release.
>
> Is it clear so far? If not, feel free to ask again :-)

Very clear, thank you :)
In fact I wanted to try adding an option in mgetty, like:
"if WITH_USR=yes, then patch the mgetty source"

### OT
(my USR Message Modem does not work well with voice+fax: received faxes 
are not well scaled but if using fax only mode with mgetty, the output 
is good; I think there's a problem when the modem is going from voice 
mode to fax mode... by the way if anyone is using this type of modem 
without problem with voice+fax, let me know, I won't even have to patch 
the sources :) ).
###

I'll have alook at the porters handbook.

> Yes, on you own machine you can have each directory you want. If you
> want to change something in the ports structure, you should ask the
> PortManagers at [EMAIL PROTECTED] and substantiate your
> requirement.

OK, but if I cvsup, won't my directory be erased ?

> Hope it helps a little bit.

I does, thanks a lot :)

Antoine
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/E9hdY3Hnhkr+5cQRAuXSAJ9NLv9KzlLflJjLHv7/XeGptzRwvQCfVu4T
hrzmQSF/cm10CQYd1U33qZA=
=xkAY
-END PGP SIGNATURE-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: question about ports

[Jens Rehsack]

Antoine Jacoutot wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello :)

I have 2 questions concerning the ports.

1. I need to apply a patch to a port so my modem could work with 
mgetty+sendfax; how do I do that ? Do I have to edit the Makefile or 
pass options to the make command ?
That's quite easy. See FreeBSD Porter's Handbook at 


Than you should check where your patch is to be applied to, either to 
the port (eg. for upgrading or fix fbsd specific behaviour) or to the 
original sources? If you can answer the first question with true, you 
should patch the according files, you know which. If the second answer 
is true, you should send your patches to the author/mailing list of the 
original sources.

Just to give you an example.
a) If I want to have the FreeBSD php4-port is able to work with thttpd,
   I have to update the lang/php4/Makefile and lang/php4/bsd.php.mk to
   recognize a new flag for the port and choosing it's dependencies
   right. This patch I will send to the FreeBSD Gnats database and to
   the ports maintainer using send-pr(1).
b) If I want php - just as example - be able to use libpopt (option
   parsing library, better than getopt()), I have to patch php and
   please the php developers to include the patch into the next release.
Is it clear so far? If not, feel free to ask again :-)

2. Can I have a port directory, like /usr/ports/personnal (or in another 
place), of my own that I can add to the regular ports tree ?
Yes, on you own machine you can have each directory you want. If you 
want to change something in the ports structure, you should ask the 
PortManagers at [EMAIL PROTECTED] and substantiate your requirement.

Thanks in advance for your answer.

Hope it helps a little bit.
Jens
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

question about ports

[Antoine Jacoutot]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello :)

I have 2 questions concerning the ports.

1. I need to apply a patch to a port so my modem could work with 
mgetty+sendfax; how do I do that ? Do I have to edit the Makefile or 
pass options to the make command ?

2. Can I have a port directory, like /usr/ports/personnal (or in another 
place), of my own that I can add to the regular ports tree ?

Thanks in advance for your answer.

Regards...

- -- 
Antoine Jacoutot
[EMAIL PROTECTED]
http://www.lphp.org
pgp key: http://www.lphp.org/ressources/ajacoutot.asc
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/E9BqY3Hnhkr+5cQRAjZLAJ9zGvD7sYRQdelDy8F59pzrKDsaHwCdGXwN
zF85ob6l1raAplvVNXHJrFY=
=3RoF
-END PGP SIGNATURE-

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: a simple question about ports

[Cliff Sarginson]

On Sun, Mar 02, 2003 at 01:42:31PM -0600, Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> > On Sun, Mar 02, 2003 at 12:39:13PM -0600, Mike Meyer wrote:
> > > In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> > > > Why are ports sometimes released, when they are uncompileable ?
> > > Lots of different reasons, the most likely one being that they
> > > compiled fine on the committers box.
> > And aye there's the rub.
> 
> I've found that most maintainers are willing to try and fix ports that
> don't compile in your environment. You can't expect a bug to be fixed
> unless you report it to someone who can fix it.
> 
Let us straighten a few things out here, the perpetuation of this kind of
nonsense puts us back in the dark Lord of Redmond world.

A language is a language. Ok GCC has groovy extras to allow FreeBSD and
Linux to compile.  
I expect that "Hello. world" will compile   
link and run .. yes ?
Does it matter very much what CPU I have, how much memory etc..?
Linking, Now we have another story.
It is quite educational to find thet KDE has a dependency on a game
program ;) Yup it sure does.
I know people put in precious spare time to just about the best OS on
the planet.
But "portupgrade" just does not hack it.
Ok. End of story. Otherwise I will get banned again by the inner corpus.
Let us make it better.

-- 
Regards
   Cliff

[ This mail has been checked as virus-free ]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: a simple question about ports

[Mike Meyer]

In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> On Sun, Mar 02, 2003 at 12:39:13PM -0600, Mike Meyer wrote:
> > In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> > > Why are ports sometimes released, when they are uncompileable ?
> > Lots of different reasons, the most likely one being that they
> > compiled fine on the committers box.
> And aye there's the rub.

I've found that most maintainers are willing to try and fix ports that
don't compile in your environment. You can't expect a bug to be fixed
unless you report it to someone who can fix it.

  http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: a simple question about ports

[Cliff Sarginson]

On Sun, Mar 02, 2003 at 12:39:13PM -0600, Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> > Why are ports sometimes released, when they are uncompileable ?
> 
> Lots of different reasons, the most likely one being that they
> compiled file on the committers box.
> 
And aye there's the rub.

-- 
Regards
   Cliff

[ This mail has been checked as virus-free ]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: a simple question about ports

[Dan Nelson]

In the last episode (Mar 02), Cliff Sarginson said:
> Why are ports sometimes released, when they are uncompileable ?

More details please.

-- 
Dan Nelson
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: a simple question about ports

[Mike Meyer]

In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> Why are ports sometimes released, when they are uncompileable ?

Lots of different reasons, the most likely one being that they
compiled file on the committers box.

  http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

a simple question about ports

[Cliff Sarginson]

Why are ports sometimes released, when they are uncompileable ?

-- 
Regards
   Cliff

[ This mail has been checked as virus-free ]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message