Date: Sat, 19 Dec 2009 12:02:08 +0100 From: Martin Wilke <miwi@FreeBSD.org> To: Paul Schmehl <pschmehl_lists@tx.rr.com> Cc: glarkin@FreeBSD.org, Sylvio Cesar Teixeira <sylvio@FreeBSD.org>, Nikola Le??i?? <nikola.lecic@anthesphoria.net>, Freebsd Ports <FreeBSD-ports@FreeBSD.org>, portmgr@freebsd.org Subject: Re: Need help with a port Message-ID: <20091219110207.GF51542@bsdcrew.de> In-Reply-To: <DC10F43194BF2E7343A700E6@Macintosh-2.local> References: <C75E8A856EACF493AC12BE4B@Macintosh-2.local> <200912180551.nBI5pHS9070032@anthesphoria.net> <89630D83B6FFCFDE388CABE9@utd65257.utdallas.edu> <4B2C0BEF.1000507@FreeBSD.org> <DC10F43194BF2E7343A700E6@Macintosh-2.local>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Dec 18, 2009 at 07:16:37PM -0600, Paul Schmehl wrote:
> --On December 18, 2009 5:10:39 PM -0600 Greg Larkin <glarkin@FreeBSD.org>
> wrote:
> >
> > Hi Paul,
> >
> > "make -V BINMODE" returns "555", so as long as you're OK with those
> > permissions, I would say using the ${BINMODE} macro is preferable.
> > Otherwise, there's no issue with you using the correct permissions value
> > (755, +x, etc.) for your situation.
> >
> > If you're having difficulty getting your port committed because you have
> > a construct that is used in many other ports, I think you can ask for
> > portmgr's opinion. They will certainly resolve the issue for you.
> > IMHO, I don't see any problem with what you're doing.
> >
> > If your committer has not responded to you in some number of weeks, you
> > can also ask portmgr to reassign the port back to the pool or to another
> > willing committer.
> >
>
> My committer asked:
>
> > Why is necessary chmod to 755? Why need it?
>
> I answered:
>
> > Because the install-sh script has incorrect permissions and generates an
> error if you don't set them correctly.
>
> The committer submitted my response to another person who wrote:
>
> > I'm sorry that's the wrong way to fix that, the premission problem come
> > from the configure script, run in the same problem a year ago. Check
> > games/wormux-devel there is a fix for the same problem maybe you can
> > take the same way.
>
> I asked for clarification about a month ago. I looked at the port he
> referred to, but I don't see how it applies to my situation. So I stated
> that and asked for help. None has been forthcoming, but I haven't pushed
> it either. I know everyone is busy. I certainly am. And we're all
> volunteers as well. So, I'm not complaining. I just want to understand
> what the right way is to solve this particular problem and get the port
> committed.
>
> I've cc'd both of them as well as portmgr. I'll do whatever I'm told to
> do.
Hi Paul,
I'm sorry, sylivo@ is still on wedding vacation,
his inet access is very limited for this time.
I already wrote to you on 18 DEC after getting
your FW: ...
- - Martin
PS:
portmgr isn't necessarily here.
>
> Paul Schmehl, If it isn't already
> obvious, my opinions are my own
> and not those of my employer.
> ******************************************
> WARNING: Check the headers before replying
>
> _______________________________________________
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
>
- --
+-----------------------+-------------------------------+
| PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| Skype : splash_111 | Mail : miwi(at)FreeBSD.org |
+-----------------------+-------------------------------+
| Mess with the Best, Die like the Rest! |
+-----------------------+-------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (FreeBSD)
iEYEARECAAYFAksssq8ACgkQdLJIhLHm/Onf1wCfXrhjUodtlXz4bBdginV4/RW5
9HMAnjC9obmEsQr3/biyilYBoggq5Fud
=DOLu
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091219110207.GF51542>