Re: HOW-TO get Flash7 working!

[Boris Samorodov]

On Thu, 17 Jan 2008 19:09:12 -0800 (PST) Tim Clewlow wrote:

> How about a compromise. Find a relatively simple linux port that breaks heir
> style/policy. Fix it, send in a patch giving the reason that it used to break
> heir style/policy and now with the patch it doesnt.

Compromise? Pardon me, but have you read the thread? You ask much
_more_ than I do! I ask only to show _instructions_ how to fix a
broken port.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: HOW-TO get Flash7 working!

[Tim Clewlow]

--- Jeremy Messenger <[EMAIL PROTECTED]> wrote:

> On Thu, 17 Jan 2008 12:21:47 -0600, Michal Varga <[EMAIL PROTECTED]>  
> wrote:
> 
> >
> > On Thu, 2008-01-17 at 20:24 +0300, Boris Samorodov wrote:
> >
> >> Please, prove that you are right. Or do you want to receive a hammer
> >> without doing it?
> >>
> > And why not? Give him the approval to do the patches, review them and if
> > he is right in his approach and they work as they should, commit them?
> 
> 
> How can we approve to something nothing? Do you realized that anyone  
> doesn't need anyone's approve to create the patches? Chuck hasn't provide  
> any patch, edvince nor detail. His words:
> 
> Date: Mon, 14 Jan 2008 15:08:50 -0500
> From: Chuck Robey <[EMAIL PROTECTED]>
> ==
> The only way I'm going to get things to be for certain, it's to start over
>  from the beginning, and this time follow the procedures that any serious
> porter (such as you) already knows by heart.   I'm not going to try to
> repeat all that here.
> ==
> 
> Cheers,
> Mezz
> 
> > m.
> 

How about a compromise. Find a relatively simple linux port that breaks heir
style/policy. Fix it, send in a patch giving the reason that it used to break
heir style/policy and now with the patch it doesnt. Then you will be in a
better position to present your reasoning to a port manager if the maintainer
complains. And, assuming the port manager will approve of a port being made
heir compliant, you will then have a precedent to back you up, and may be more
able to convince a port manager to give you approval/backing to do the whole
lot.

Cheers, Tim.


  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

You have been unsubscribed from the uma1 mailing list

[uma1-bounces]

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

FreeBSD Port: devel/bouml

[V.Chukharev]

Hi maintainer,

I do not know the reason, but devel/bouml (cvsup'ed yesterday) cannot fetch the 
distfile.
I think that it has been updated or something on the main web site.

MD5 shown below is same as shown on their site, SHA256 and SIZE I found from the
downloaded file. It builds OK, starts, and works - to the extent I could check 
within
10 minits.

Best regard,
Vladimir Chukharev

$ cat /usr/ports/devel/bouml/distinfo
MD5 (bouml_3.5.tar.gz) = cd13f4b1e5fad2f3c64bb827e8d6418a
SHA256 (bouml_3.5.tar.gz) = 
b966e56ee642cd77be180e38c31d86cd103423154e6458f50dc6f173101af017
SIZE (bouml_3.5.tar.gz) = 4157379
-- 
V. Chukharev
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: new wiki page: State of Packages on Sparc64

[Marius Strobl]

On Tue, Jan 08, 2008 at 08:03:01PM -0800, Stephen Hurd wrote:
> Marius Strobl wrote:
> >FYI, it's fixed by the following commit:
> >http://docs.freebsd.org/cgi/mid.cgi?200711051136.lA5BaHpL069527
> >
> >Marius
> 
> Looks like a low chance of it making it into 7.0-RELEASE?

No, it actually got approved. Currently we're just waiting for
a universe build test to finish.

Marius

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

Re: Oracle SQL Developer

[Jose Garcia Juanino]

El jueves 17 de enero a las 20:48:39 CET, Scott T. Hildreth escribió:
> 
> On Sun, 2008-01-13 at 21:56 +0100, martinko wrote:
> > Marcin Cieslak wrote:
> > > martinko wrote:
> > >> Hallo,
> > >>
> > >> Would someone care to port Oracle's SQL Developer to FreeBSD, please ?
> > >>
> > >> 
> > >>
> > >>
> > >> Many thanks in advance!
> > > 
> > > There is actually nothing to port, just download the non-JRE platform
> > > independent zip file, unpack and run "bash sqldeveloper" from
> > > sqldeveloper/sqldeveloper/bin directory.
> > > 
> > > Works for me (7.0-BETA3 on amd64, self-compiled sun jdk15 from ports).
> > > 
> > > --Marcin
> > > 
> > 
> > 
> > Well,
> > 
> > I've tried it on 6-STABLE (6.2.something) and it got stuck at splash 
> > screen.  Btw, I've noticed output like this in terminal:
> 
>   When I first ran it, I had the same problem.  Then I noticed that
> there was a prompt window behind the splash screen.  I was able to 
> grab the edge and pull the window over and answer the prompt.

In my window manager I was able to move that window to another place and
answer "No" to the question. The window is hidden by the splash screen,
but it is possible to move it by mean of the menu window in the task
bar.

> 
> > 
> > expr: illegal option -- X
> > usage: expr [-e] expression
> > expr: illegal option -- D
> > usage: expr [-e] expression
> > 
> 
>   Linux expr has different options then the FreeBSD expr.  I ignore 
>   these errors since they are testing paths and my install is working.

A workaround is to prefix the arguments of expr command with
a double hyphen (--)

> > Also, all the scripts use #!/bin/bash which doesn't work in FreeBSD.

It does not matter as the script are executed under sh shell:

$ sh sqldeveloper

>   I wrote a wrapper script to handle this,
> 
> =
> 
> #!/usr/local/bin/zsh
> 
> cd ~/src/Java/sqldeveloper/sqldeveloper/bin/
> bash ./sqldeveloper $@
> 
> =
> 
> ...you could also link /usr/local/bin/bash to /bin/bash.

I think it would be possible to run sqldeveloper without any reference
to bash shell. I have submitted a problem report to port sqldeveloper:

http://www.freebsd.org/cgi/query-pr.cgi?pr=119756

Any feedback will be appreciated.


Regards


pgpOJ1OvIoRFc.pgp
Description: PGP signature

Re: Oracle SQL Developer

[Scott T. Hildreth]

On Sun, 2008-01-13 at 21:56 +0100, martinko wrote:
> Marcin Cieslak wrote:
> > martinko wrote:
> >> Hallo,
> >>
> >> Would someone care to port Oracle's SQL Developer to FreeBSD, please ?
> >>
> >> 
> >>
> >>
> >> Many thanks in advance!
> > 
> > There is actually nothing to port, just download the non-JRE platform
> > independent zip file, unpack and run "bash sqldeveloper" from
> > sqldeveloper/sqldeveloper/bin directory.
> > 
> > Works for me (7.0-BETA3 on amd64, self-compiled sun jdk15 from ports).
> > 
> > --Marcin
> > 
> 
> 
> Well,
> 
> I've tried it on 6-STABLE (6.2.something) and it got stuck at splash 
> screen.  Btw, I've noticed output like this in terminal:

  When I first ran it, I had the same problem.  Then I noticed that
there was a prompt window behind the splash screen.  I was able to 
grab the edge and pull the window over and answer the prompt.

> 
> expr: illegal option -- X
> usage: expr [-e] expression
> expr: illegal option -- D
> usage: expr [-e] expression
> 

  Linux expr has different options then the FreeBSD expr.  I ignore 
  these errors since they are testing paths and my install is working.

> Also, all the scripts use #!/bin/bash which doesn't work in FreeBSD.

  I wrote a wrapper script to handle this,

=

#!/usr/local/bin/zsh

cd ~/src/Java/sqldeveloper/sqldeveloper/bin/
bash ./sqldeveloper $@

=

...you could also link /usr/local/bin/bash to /bin/bash.

   
> And I'd like to install it in /usr/local/... so that all users can use 
> it and it can be included in portaudit checks and checked for upgrades 
> via ports system, etc etc.
> 
> Thanks,
> 
> Martin
> 
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-database
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: HOW-TO get Flash7 working!

[Jeremy Messenger]

On Thu, 17 Jan 2008 12:21:47 -0600, Michal Varga <[EMAIL PROTECTED]>  
wrote:




On Thu, 2008-01-17 at 20:24 +0300, Boris Samorodov wrote:


Please, prove that you are right. Or do you want to receive a hammer
without doing it?


And why not? Give him the approval to do the patches, review them and if
he is right in his approach and they work as they should, commit them?



How can we approve to something nothing? Do you realized that anyone  
doesn't need anyone's approve to create the patches? Chuck hasn't provide  
any patch, edvince nor detail. His words:


Date: Mon, 14 Jan 2008 15:08:50 -0500
From: Chuck Robey <[EMAIL PROTECTED]>
==
The only way I'm going to get things to be for certain, it's to start over
from the beginning, and this time follow the procedures that any serious
porter (such as you) already knows by heart.   I'm not going to try to
repeat all that here.
==

Cheers,
Mezz


m.



--
[EMAIL PROTECTED]  -  [EMAIL PROTECTED]
FreeBSD GNOME Team  -  FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/  -  [EMAIL PROTECTED]
http://wiki.freebsd.org/multimedia  -  [EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: HOW-TO get Flash7 working!

[Michal Varga]

On Thu, 2008-01-17 at 20:24 +0300, Boris Samorodov wrote:

> Please, prove that you are right. Or do you want to receive a hammer
> without doing it?
> 
And why not? Give him the approval to do the patches, review them and if
he is right in his approach and they work as they should, commit them?


> Actually, I don't understand what you don't understand. The thread
> becomes a little bit annoying to me. :-(
> 
Well, I may be just a lurking nobody, but I think I can see his point
clearly. He doesn't want to commit his (probably not insignificant) time
and resources to a full-scale solution just to be turned down when he
gets back with all the work done, with a simple "thank you, but you
shouldn't have done all this without asking us if we are interested,
actually, this is too radical for us, we don't want it, this would upset
a number of port maintainers, yadda yadda, no thank you, bye".

I don't think there are people every day offering you that they will do
a job like moving every single linux port to /compat/ just like that for
free, and the only thing he is asking for is that there is somebody who
will officially back him up. He doesn't want to spend next 150 years
arguing with every single linux port maintainer if his approach is wrong
or right, he is looking for someone "up there" who can look at his idea,
say "hey, this looks interesting, do it, if you can make it work, we
will issue a new porting guidelines and deal with the maintainers". And
he does sound quite reasonable.


m.

-- 
Michal Varga <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
Stonehenge

Home page: http://varga.stonehenge.sk

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

Re: HOW-TO get Flash7 working!

[Boris Samorodov]

On Wed, 16 Jan 2008 14:34:23 -0500 Chuck Robey wrote:
> Boris Samorodov wrote:
> > On Tue, 15 Jan 2008 16:10:15 -0500 Chuck Robey wrote:
> > 
> >> All those libraries need to be found
> >> by the flash9 plugin library.
> > 
> > Please, give me strict instructions how to repeate (what to do
> > after a fresh install):
> > -
> > 0. Fresh RELENG_X_Y install.
> > 2. Fresh ports (or date=...).
> > 3. ...

> I said at the very beginning of this thread, that I didn't keep track of
> what I did, because the tack I took was to relocate all of the libs to the
> /compat tree, and this sort of strategy can't be taken until I could get
> official approval of that as the correct method to take for installation of
> Linux libraries.

Catch 22? You won't do anything without official approvement but you
won't get an official approvement without proving you are right...

> If I got that approval, I said I would undertake to
> locate and fix all of the ports that currently install Linux stuff into the
> /usr/local tree, and then make the flash9 work.  This sort of tack can't be
> attempted, unless I could show the port authors involved that I have
> official approval to get this thing done, so they could either approve of
> the diffs I would give them, or argue it with the port managers themselves.
>  What I never, ever intended to try, was to force things in any way, that's
> acting childishly.  I just needed a official hammer that was morally strong
> enough to get things moving.

Please, prove that you are right. Or do you want to receive a hammer
without doing it?

> In fact, if it were understood that I was to get that sort of ruling in
> advance, then I would agree to submit complete diffs, in advance of the

Patches will be good, but firstly it would be enough to give just
instructions which one can follow (see a quote at the very
beginning).

> work, both so folks could look at them, and so it could be proven that this
> strategy does indeed get the flash9 working.  I'm not terribly worried
> about doing that, because I did it on my system already, and the only worry
> for me is if things (in the meantime) might have changed enough to make
> this no longer possible.

> But without that?  I would be condemned to endless arguments, in order to
> effect all the changes, and I don't like arguing that much.  No, I am not
> going to contribute to a tack that I feel is wrong-headed.  I won't get in
> your way, but I wouldn't contribute to that.

> I hope that's a reasonably honest approach.  To be REALLY stict about it,
> what I'm most strict about is getting all Linux libraries into the /compat
> tree, and probably doing that alone would be sufficient, but I'm trying
> here for the whole boat, moving all Linux things into /compat, as the
> hier(7) dictates (as I read it),

Hier gurus may not read [EMAIL PROTECTED]

> and for the reasons that I've given
> endlessly by now.

I didn't see any _proved_ reason. Is there somebody out there who did?

> In fact, I think it's a fact that I've really given this all the airing
> that's really needed.  If folks can't see it's needed after all this, then
> go ahead and live with it, as long as I can make my system my way.  I will
> no longer feel bad about it, I gave it a fair try at sharing what I felt
> was the right way to do things.  I have asked a bunch of times (both in
> this thread, and in one direct mail to them) to get one of the port
> managers to issue a ruling, but I think I will take being ignored as a de
> facto ruling.  I don't wish to harangue folks any longer.

Actually, I don't understand what you don't understand. The thread
becomes a little bit annoying to me. :-(

If can prove that you are right just do it. Please.
If you can't (or don't want or else) it's also OK. Please.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: mysql-server-5.0.51

[Jeremy Chadwick]

On Thu, Jan 17, 2008 at 11:01:24AM -0500, Michael Boers wrote:
> I am not sure what the proper procedure for this is, but I would like to 
> suggest that the following patch be added to the mysql50-server port.  It 
> seems as if 5.0.51 contains a bug that prevents ssl connections.  I am 
> including a patch taken from http://bugs.mysql.com/bug.php?id=33292 and 
> modified to patch the file namespace of the port.  This bug cost me several 
> hours, perhaps this can save the next guy some time.
>
> Please see http://bugs.mysql.com/bug.php?id=33292 for details of the bug 
> and discussion of the fix.

I second this patch addition.  I've read the bug, and the fix looks
completely proper.  How this managed to slip past the MySQL folks, we'll
probably never know...

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

FreeBSD Port: mysql-server-5.0.51

[Michael Boers]

I am not sure what the proper procedure for this is, but I would like  
to suggest that the following patch be added to the mysql50-server  
port.  It seems as if 5.0.51 contains a bug that prevents ssl  
connections.  I am including a patch taken from http://bugs.mysql.com/ 
bug.php?id=33292 and modified to patch the file namespace of the  
port.  This bug cost me several hours, perhaps this can save the next  
guy some time.


Please see http://bugs.mysql.com/bug.php?id=33292 for details of the  
bug and discussion of the fix.


Thanks,

Michael Boers

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

Re: bsd.php.mk suggestion

[Vladimir Zorin]

Alex Dupre wrote:

Vladimir Zorin ha scritto:
Yes, the patch you mentioned above is exactly what I've been talking 
about! It'd be great if you commit it. Thank you!


I will wait for a couple of "I tested it and it works as expected", 
before committing it.




Well, it is exactly the same patch we are using at our company, line by
line, the only difference is in the name of the variable - in your patch
it is called PHPBASE, in our working variant - WITH_PHP.
So I may say we've been using this patch for quite a while already, and
it works as expected.

Hopefully there will be more replies from the others too.



Best regards, Vladimir Zorin

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

Re: bsd.php.mk suggestion

[Alex Dupre]

Vladimir Zorin ha scritto:
Yes, the patch you mentioned above is exactly what I've been talking 
about! It'd be great if you commit it. Thank you!


I will wait for a couple of "I tested it and it works as expected", 
before committing it.


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

Re: bsd.php.mk suggestion

[Vladimir Zorin]

Alex Dupre wrote:

Vladimir Zorin ha scritto:

It's a common need, especially among internet-hosting providers, to have
several different PHP versions installed on a server.


I'd like to remember that php4 is EOL.


Well, if only we lived in an ideal world...But in reality one often has 
to use specific software long after it's out of production and 
maintenance. Sometimes it is a whim, sometimes it is a need, it depends...


In my humble opinion it would do lots of good and save lots of efforts 
if this patch could be incorporated into the default bsd.php.mk - 
people who don't need to install several php versions will not be 
affected

at all, but those who do will only gain.


Can you try the following patch?

http://www.alexdupre.com/bsd.php.mk.patch

Since it shouldn't hurt common users I will commit it in the next days 
if you confirm me that's ok.


Yes, the patch you mentioned above is exactly what I've been talking 
about! It'd be great if you commit it. Thank you!


--
Best regards, Vladimir Zorin

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

Re: bsd.php.mk suggestion

[Alex Dupre]

Vladimir Zorin ha scritto:

It's a common need, especially among internet-hosting providers, to have
several different PHP versions installed on a server.


I'd like to remember that php4 is EOL.

In my humble opinion it would do lots of good and save lots of efforts 
if this patch could be incorporated into the default bsd.php.mk - people 
who don't need to install several php versions will not be affected

at all, but those who do will only gain.


Can you try the following patch?

http://www.alexdupre.com/bsd.php.mk.patch

Since it shouldn't hurt common users I will commit it in the next days 
if you confirm me that's ok.


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

Re: bsd.php.mk suggestion

[Bill Moran]

In response to Vladimir Zorin <[EMAIL PROTECTED]>:

> Bill Moran wrote:
> > In response to Dominic Fandrey <[EMAIL PROTECTED]>:
> > 
> >> Vladimir Zorin wrote:
> >>> I tried to get in touch with Alex Dupre, the maintainer of the
> >>> bsd.php.mk, sent him the same text as the above with the patch, but I
> >>> didn't get any response. As far as I know there are several people who
> >>> tried to contact him regarding the same issue but, alas, didn't get any
> >>> response as well.
> >> I suppose there might be the possibility of a timeout that allows 
> >> committing
> >> without Maintainer feedback, if you submit it as a PR.
> > 
> > This is exactly the way to proceed.
> > 
> > If the maintainer is not responding, open the issue as a PR so it's
> > officially tracked.  If the maintainer does not respond withing a
> > reasonable length of time, request a maintainer timeout to have another
> > committer check in the patch.
> 
> Thank you for the tip, I'll do the way you described. What regards 
> "reasonable length of time" - a fortnight, for example, is reasonable 
> enough?

There is an actual documented policy on this:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-maintainer.html

-- 
Bill Moran
http://www.potentialtech.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

can not upgrade samba3

[Tim TB. Boven]

I tried to upgrade to Samba 3.0.28,1 today but without any luck.

I did a re-run any copied the output below.
I configured the port to install Samba with support for kerberos (Heimdal is 
installed).

I'm unable to figure out what the cause of this error is or how to solve it.
Any idea to solve this?

Tim

===>  Building for samba-3.0.28,1
cd /usr/ports/net/samba3/work/samba-3.0.28/source && make pch
rm -f /usr/ports/net/samba3/work/samba-3.0.28/source/include/includes.h.gch
cc -I. -I/usr/ports/net/samba3/work/samba-3.0.28/source  -O2 
-fno-strict-aliasin g -pipe 
-D_SAMBA_BUILD_=3 -I/usr/local/include  -I/usr/ports/net/samba3/work/sam
 ba-3.0.28/source/iniparser/src -Iinclude 
-I./include  -I. -I. -I./lib/replace -I 
./lib/talloc -I./tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H  
-I/usr/loc al/include 
-DLDAP_DEPRECATED-I/usr/ports/net/samba3/work/samba-3.0.28/source   
  /lib -D_SAMBA_BUILD_=3 -fPIC -DPIC -c 
/usr/ports/net/samba3/work/samba-3.0.28/so  
   urce/include/includes.h -o 
/usr/ports/net/samba3/work/samba-3.0.28/source/includ   
  e/includes.h.gch
Using FLAGS  =  -O2 -fno-strict-aliasing -pipe -D_SAMBA_BUILD_=3 
-I/usr/loca l/include  
-I/usr/ports/net/samba3/work/samba-3.0.28/source/iniparser/src -Iincl   
  ude -I./include  -I. -I. -I./lib/replace 
-I./lib/talloc -I./tdb/include -I./liba 
ddns -I./librpc -DHAVE_CONFIG_H  -I/usr/local/include -DLDAP_DEPRECATED
-I/us 
r/ports/net/samba3/work/samba-3.0.28/source/lib -D_SAMBA_BUILD_=3
  PICFLAG= -fPIC -DPIC
  LIBS   = -lcrypt -lexecinfo -liconv
  LDFLAGS= -pie -Wl,-R/usr/local/lib -L/usr/local/lib -L/usr/local/lib
  DYNEXP = -Wl,--export-dynamic
  LDSHFLAGS  = -shared -Wl,-R/usr/local/lib -L/usr/local/lib 
-L/usr/local/li b
  SHLIBEXT   = so
  SONAMEFLAG = -Wl,-soname,
Compiling libsmb/clikrb5.c
libsmb/clikrb5.c: In function `krb5_set_real_time':
libsmb/clikrb5.c:128: error: dereferencing pointer to incomplete type
libsmb/clikrb5.c:129: error: dereferencing pointer to incomplete type
The following command failed:
cc -I. -I/usr/ports/net/samba3/work/samba-3.0.28/source  -O2 
-fno-strict-aliasin g -pipe 
-D_SAMBA_BUILD_=3 -I/usr/local/include  -I/usr/ports/net/samba3/work/sam
 ba-3.0.28/source/iniparser/src -Iinclude 
-I./include  -I. -I. -I./lib/replace -I 
./lib/talloc -I./tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H  
-I/usr/loc al/include 
-DLDAP_DEPRECATED-I/usr/ports/net/samba3/work/samba-3.0.28/source   
  /lib -D_SAMBA_BUILD_=3 -fPIC -DPIC -c 
libsmb/clikrb5.c -o libsmb/clikrb5.o
*** Error code 1

Stop in /usr/ports/net/samba3/work/samba-3.0.28/source.
*** Error code 1

Stop in /usr/ports/net/samba3.
*** Error code 1

Stop in /usr/ports/net/samba3.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: bsd.php.mk suggestion

[Wesley Shields]

On Thu, Jan 17, 2008 at 05:52:54PM +0300, Vladimir Zorin wrote:
> Bill Moran wrote:
>> In response to Dominic Fandrey <[EMAIL PROTECTED]>:
>> 
>>> Vladimir Zorin wrote:
 I tried to get in touch with Alex Dupre, the maintainer of the
 bsd.php.mk, sent him the same text as the above with the patch, but I
 didn't get any response. As far as I know there are several people who
 tried to contact him regarding the same issue but, alas, didn't get any
 response as well.
>>> I suppose there might be the possibility of a timeout that allows committing
>>> without Maintainer feedback, if you submit it as a PR.
>> 
>> This is exactly the way to proceed.
>> 
>> If the maintainer is not responding, open the issue as a PR so it's
>> officially tracked.  If the maintainer does not respond withing a
>> reasonable length of time, request a maintainer timeout to have another
>> committer check in the patch.
> 
> Thank you for the tip, I'll do the way you described. What regards 
> "reasonable length of time" - a fortnight, for example, is reasonable 
> enough?

The default timeout is 14 days (so yes, a fortnight).  In your case it
may be longer before it's committed since it's a change to something in
Mk.  Either way, getting it into GNATS so it can be properly tracked and
analyzed by the proper people is the right thing to do.

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

Re: bsd.php.mk suggestion

[Vladimir Zorin]

Jeremy Chadwick wrote:

On Thu, Jan 17, 2008 at 12:29:17PM +0300, Vladimir Zorin wrote:

It's a common need, especially among internet-hosting providers, to have
several different PHP versions installed on a server. ...


I think your request is fair, and I have no real problem with it.
However, I do often question why people have multiple versions of PHP
installed; it seems unnecessary with how badly-written PHP is to begin
with (that is to say, the API may change, but usually the PHP authors
simply add a new API function rather than break/tinker with existing
ones).


One of the reasons here (actually, i would say the only one :) is a 
user's request - after all, we host people,

they have different tastes and habits, they use different software which
may need specific php-version and so on.
Of course, with a bit of handwork you can get almost any software to 
work with that php version that you have installed. But you know people. 
Old habits die hard.
Say, one user is used to php4. And doesn't want to migrate to php5 
because: it's not stable, it's bad-coded, or whatever this person thinks 
of php5. And another is used to php5. And believes it's all the voque 
and staff. And they are hosted on a same machine.

We host these people, and this means that we have to provide them with
some space on our servers and with the ability to install and use the 
software they used to. We can't tell each and everyone on how to get 
his/her favorite software working with php5 or php4 - there are just too 
many users and a very small bunch of tech.support guys ;)


And as I've mentioned before - there's only a minor change to the 
bsd.php.mk file, which would seriously ease the process of multiple 
php-versions installation and wouldn't affect the people who don't need 
this.



--
Best regards, Vladimir Zorin

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

Re: bsd.php.mk suggestion

[Vladimir Zorin]

Bill Moran wrote:

In response to Dominic Fandrey <[EMAIL PROTECTED]>:


Vladimir Zorin wrote:

I tried to get in touch with Alex Dupre, the maintainer of the
bsd.php.mk, sent him the same text as the above with the patch, but I
didn't get any response. As far as I know there are several people who
tried to contact him regarding the same issue but, alas, didn't get any
response as well.

I suppose there might be the possibility of a timeout that allows committing
without Maintainer feedback, if you submit it as a PR.


This is exactly the way to proceed.

If the maintainer is not responding, open the issue as a PR so it's
officially tracked.  If the maintainer does not respond withing a
reasonable length of time, request a maintainer timeout to have another
committer check in the patch.


Thank you for the tip, I'll do the way you described. What regards 
"reasonable length of time" - a fortnight, for example, is reasonable 
enough?


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

Re: bsd.php.mk suggestion

[Bill Moran]

In response to Dominic Fandrey <[EMAIL PROTECTED]>:

> Vladimir Zorin wrote:
> > I tried to get in touch with Alex Dupre, the maintainer of the
> > bsd.php.mk, sent him the same text as the above with the patch, but I
> > didn't get any response. As far as I know there are several people who
> > tried to contact him regarding the same issue but, alas, didn't get any
> > response as well.
> 
> I suppose there might be the possibility of a timeout that allows committing
> without Maintainer feedback, if you submit it as a PR.

This is exactly the way to proceed.

If the maintainer is not responding, open the issue as a PR so it's
officially tracked.  If the maintainer does not respond withing a
reasonable length of time, request a maintainer timeout to have another
committer check in the patch.

-- 
Bill Moran
http://www.potentialtech.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: bsd.php.mk suggestion

[Jeremy Chadwick]

On Thu, Jan 17, 2008 at 12:29:17PM +0300, Vladimir Zorin wrote:
> It's a common need, especially among internet-hosting providers, to have
> several different PHP versions installed on a server. ...

I think your request is fair, and I have no real problem with it.
However, I do often question why people have multiple versions of PHP
installed; it seems unnecessary with how badly-written PHP is to begin
with (that is to say, the API may change, but usually the PHP authors
simply add a new API function rather than break/tinker with existing
ones).

We're a hosting provider and have never run into any issues during PHP
version migrations.  People online everywhere exhibited signs of
paranoia when it came to the PHP4 -> PHP5 upgrade, citing "major
concerns" and all sorts of other hooplah.  We migrated and absolutely no
scripts on our system were impacted.

At my workplace I did similar migration of PHP4 --> PHP5 on our
operational/systems management machines, and ran into no issues as a
result of the migration.  (I did build XML support in, which turned out
to break on our Solaris systems in an odd way, but that turned out to be
the fault of the libxml2 library installed on those boxes and not PHP).

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

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

Re: bsd.php.mk suggestion

[Dominic Fandrey]

Vladimir Zorin wrote:
> I tried to get in touch with Alex Dupre, the maintainer of the
> bsd.php.mk, sent him the same text as the above with the patch, but I
> didn't get any response. As far as I know there are several people who
> tried to contact him regarding the same issue but, alas, didn't get any
> response as well.

I suppose there might be the possibility of a timeout that allows committing
without Maintainer feedback, if you submit it as a PR.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

bsd.php.mk suggestion

[Vladimir Zorin]

Hi folks!

I'm not sure if it is the right place to post my suggestion, I hope you 
will excuse and redirect me, if it is not.


I have the following suggestion:

It's a common need, especially among internet-hosting providers, to have
several different PHP versions installed on a server. Given the current 
bsd.php.mk, it's not an easy thing to do:


Say, you have one php version successfully installed.

To install another on the same server, you would naturally do something 
like setting
PREFIX=/usr/local/php4 and then running make. PHP itself will be 
compiled and installed,
but if we try to install some php-extensions after that,  it will fail, 
because every php-extension
needs phpize for proper installation, and it tries to find it in the 
LOCALBASE, not in PREFIX directory.


Of course, you could set LOCALBASE=/usr/local/php4 and then run make. 
But this way
php would also install all the dependencies - apache, mysql and the 
like, which we actually already

have installed in the /usr/local, and which we do not need.

As far as I know, lots of people have faced this problem, and the only 
solution I know, is to patch bsd.php.mk, which seems to be quite 
reasonable. It's a minor patch, adding one option WITH_PHP
(the name, naturally, is of no matter) and changing LOCALBASE to 
WITH_PHP in several places in the

bsd.php.mk file.

In my humble opinion it would do lots of good and save lots of efforts 
if this patch could be incorporated into the default bsd.php.mk - people 
who don't need to install several php versions will not be affected

at all, but those who do will only gain.

I tried to get in touch with Alex Dupre, the maintainer of the 
bsd.php.mk, sent him the same text as the above with the patch, but I 
didn't get any response. As far as I know there are several people who 
tried to contact him regarding the same issue but, alas, didn't get any 
response as well.


So I've decided to post it here, hopefully it will help.

Best regards, Vladimir Zorin

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

Re: HOW-TO get Flash7 working!

[Michal Varga]

On Thu, 2008-01-17 at 08:50 +0100, Alexander Leidinger wrote:
> There's a different thread about flash and [EMAIL PROTECTED] reported there  
> that the plugin is loaded by firefox but crashes. I've also seen  
> reports that it doesn't crash, but I think those people where just  
> lucky and didn't use the subset of flash which triggers the crash.
> 
You can crash Flash9 on FreeBSD any time just by visiting youtube.com
and playing any random video, 100% success guaranteed.

By the way, Flash9 is buggy like hell even when running natively on
Linux, I can't confirm that by myself, but have some old coworkers in
various web development companies and they say their clients complain
every other day that their new fancy Flash9 presentations (thus
requiring Flash9 plugin) crash Linux browsers like stock market in 1929.
Of course, it's still much worse under Linuxulator.

m.

-- 
Michal Varga <[EMAIL PROTECTED]>
Stonehenge

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