Bug 80946

Summary: www/php4-mnogosearch: Mnogosearch PHP4 Extension module
Product: Ports & Packages Reporter: Radim Kolar <hsn>
Component: Individual Port(s)Assignee: Alex Dupre <ale>
Status: Closed FIXED    
Severity: Affects Only Me CC: hsn
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
php4-mnogosearch-1.96,1.shar none

Description Radim Kolar 2005-05-12 18:10:02 UTC
Mnogosearch extension for PHP language. This extesion comes from their
master site and not from PHP package itself.

WWW: http://www.mnogosearch.org/

Generated with FreeBSD Port Tools 0.63

How-To-Repeat: this is updated mnogosearch extension for php. part 2 of mnogosearch
update pack.
Comment 1 Jean-Yves Lefort freebsd_committer freebsd_triage 2005-05-13 06:33:39 UTC
Responsible Changed
From-To: freebsd-ports-bugs->ache

Over to maintainer.
Comment 2 Andrey A. Chernov freebsd_committer freebsd_triage 2005-05-13 06:40:07 UTC
Responsible Changed
From-To: ache->freebsd-ports

This PR is misadderssed. I don't wish to maintain that code base 
and ask for repo-copy right now.
Comment 3 Sam Lawrance freebsd_committer freebsd_triage 2005-05-18 14:41:08 UTC
Responsible Changed
From-To: freebsd-ports->lawrance

Grab
Comment 4 Sergey Matveychuk freebsd_committer freebsd_triage 2005-05-21 17:12:51 UTC
It's a very undesirable PR.

1) I can't see from the PR why the existent port must be dropped?
2) If it is necessary, the PR should provide an unify diff to the old 
port. If it's unnecessary, another dir name should be used.
3) The new port has no maintainer.

--
Sem.
Comment 5 Sam Lawrance freebsd_committer freebsd_triage 2005-05-22 04:10:20 UTC
On Sat, 2005-05-21 at 16:20 +0000, Sergey Matveychuk wrote:
> The following reply was made to PR ports/80946; it has been noted by GNATS.
> 
> From: Sergey Matveychuk <sem@FreeBSD.org>
> To: bug-followup@FreeBSD.org, hsn@netmag.cz
> Cc:  
> Subject: Re: ports/80946: [mnogosearch part 2] www/php4-mnogosearch: Mnogosearch
>  PHP4 Extension module
> Date: Sat, 21 May 2005 20:12:51 +0400
> 
>  It's a very undesirable PR.
>  
>  1) I can't see from the PR why the existent port must be dropped?
>  2) If it is necessary, the PR should provide an unify diff to the old 
>  port. If it's unnecessary, another dir name should be used.
>  3) The new port has no maintainer.

I agree, we shouldn't stomp all over ale's port :)

The current php4-mnogosearch, php5-mnogosearch and this PR all provide a
mnogosearch php extension originating from mnogosearch.org.

php4-mnogosearch and php5-mnogosearch use the extension that is bundled
with PHP.

The port in this PR uses the current source directly from
mnogosearch.org.  It should work for both php4 and php5.

Perhaps a better name/dir for this port would be
mnogosearch-php-extension or similar, which indicates that the vendor is
mnogosearch rather than php.

Radim, would you also please consider maintaining the mnogosearch ports
you have submitted and let me know?  Maintainership of www/mnogosearch
is up for grabs if you are interested, too ;)
Comment 6 Radim Kolar 2005-05-23 17:12:44 UTC
> 1) I can't see from the PR why the existent port must be dropped?
my fault. in fact we can have both mnogosearch-php4 ports in different
directories.
ports/80944 do not works with stock php4 mnogosearch extension.
> 2) If it is necessary, the PR should provide an unify diff to the old 
> port. If it's unnecessary, another dir name should be used.
okay, choose a new directory for this port.

radim
Comment 7 Radim Kolar 2005-05-24 15:10:21 UTC
> Radim, would you also please consider maintaining the mnogosearch ports you
> have submitted and let me know?  Maintainership of www/mnogosearch is up for
> grabs if you are interested, too ;)
I am not interested in maintaining of any port. My goal of life is making
spiritual progress. This precious procedure requires some time. I want to spend
my time in that kind of activity and not in maintaining some ports. Because
very few people (1:1000) want to live like this, i am sure that you will find
another maintainer without any problems.

Radim.
Comment 8 Sam Lawrance freebsd_committer freebsd_triage 2005-06-12 04:40:43 UTC
Responsible Changed
From-To: lawrance->ale

Over to maintainer.
Comment 9 Pav Lucistnik freebsd_committer freebsd_triage 2007-03-01 12:52:46 UTC
State Changed
From-To: open->closed

Close on submitter's request