Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
2011/7/14 Pav Lucistnik p...@freebsd.org: Stephen Montgomery-Smith píše v čt 14. 07. 2011 v 11:57 -0500: entry. I assume that the filename of the desktop entry is unimportant, The filename of desktop entry should be 100% inconsequential, and our only care should be not have two ports installing same file. and is used only internally by Gnome or whatever. Sounds like a bug to me. But maybe it would have been better to have had one more entry in DESKTOP_ENTRIES that was the actual filename of the desktop entry. Yes, but is it worth the effort? Note you'll have to introduce it somehow not to break existing ports. How about something like this: http://www.freebsd.org/cgi/query-pr.cgi?pr=158936 Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: p5-XML-LibXML 1.80,1
Op donderdag 14 juli 2011 19:25:59 schreef ajtiM: Problem to update p5-XML-LibXML 1.80,1 on FreebSD 8.2: I used portmaster but I did try wit make install too: (...) Can't locate XML/SAX.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/BSDPAN /usr/local/lib/perl5/site_perl/5.12.4/mach /usr/local/lib/perl5/site_perl/5.12.4 /usr/local/lib/perl5/5.12.4/mach /usr/local/lib/perl5/5.12.4 .). BEGIN failed--compilation aborted. *** Error code 2 Stop in /usr/ports/textproc/p5-XML-LibXML/work/XML-LibXML-1.80. reinstall textproc/p5-XML-SAX first ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: p5-XML-LibXML 1.80,1
On Friday 15 July 2011 04:51:43 Oliver Heesakkers wrote: /p5-XML-LibXML Thank you very much. There was one other p5* port and looks like that portmaster is not usable more for update. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: p5-XML-LibXML 1.80,1
On Fri, 15 Jul 2011 05:40:27 -0500 ajtiM articulated: Thank you very much. There was one other p5* port and looks like that portmaster is not usable more for update. I would suggest using either portupdate or portmanager. Both can handle this installation/update for you without incident. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
On Fri, 15 Jul 2011, Scot Hetzel wrote: 2011/7/14 Pav Lucistnik p...@freebsd.org: Stephen Montgomery-Smith píše v čt 14. 07. 2011 v 11:57 -0500: entry. I assume that the filename of the desktop entry is unimportant, The filename of desktop entry should be 100% inconsequential, and our only care should be not have two ports installing same file. and is used only internally by Gnome or whatever. Sounds like a bug to me. But maybe it would have been better to have had one more entry in DESKTOP_ENTRIES that was the actual filename of the desktop entry. Yes, but is it worth the effort? Note you'll have to introduce it somehow not to break existing ports. How about something like this: http://www.freebsd.org/cgi/query-pr.cgi?pr=158936 Wouldn't the point of using a separate filename argument be to let the user specify exactly what the name is? Here you end up with the same system-processed filename. Possibly I've misunderstood. Apart from whether it's necessary, making the filename the last field would simplify the code. Just .if defined(DESKTOP_ENTRIES) or defined(DESKTOP_ENTRIESv2) at the start of parameter processing, and a .if defined(DESKTOP_ENTRIESv2) section after it to override the filename. It could also be made polymorphic, basing what it does on the number of fields rather than a new DESKTOP_ENTRIESv2 define.___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What about creating an office team
On Fri, Jul 15, 2011 at 4:33 PM, Baptiste Daroussin b...@freebsd.org wrote: Hi, Is there anyone interested here to be part of an office team? the goal of that team will be to take care of the office components of the ports. Those are quite important for the desktop experience and having relying on one person being able through a team to potentially have multiple person taking care or this would be great imho. The candidate for maintenance by this team would be: editors/libreoffice editors/openoffice* (? maho@ are you interested in that?) textproc/libwps textproc/libwpd *spell* textproc/mythes textproc/hyphen devel/icu maybe many more? (you can propose your candidate here :)) Any volunteer to be part of that team if any? maybe renaming the openoffice@ to office@ should be enough regards, Bapt ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org I don't have much free time but it's certainly better than nothing. Count me in :) Regards, George ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What about creating an office team
Baptiste Daroussin wrote: [...] maybe many more? (you can propose your candidate here :)) What about math/gnumeric? It's a nice, lightweight spreadsheet if one doesn't want the `bloat' that is open-/libreoffice. Good luck with your project! Regards, Philipp
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
2011/7/15 Warren Block wbl...@wonkity.com:
How about something like this:
http://www.freebsd.org/cgi/query-pr.cgi?pr=158936
Wouldn't the point of using a separate filename argument be to let the user
specify exactly what the name is? Here you end up with the same
system-processed filename. Possibly I've misunderstood.
The system-processed filename could be simplified for the
DESKTOP_ENTRIESv2 in install-desktop-entries to just
filename=$$1
But then we would still need to add a check to check-desktop-entries
for DESKTOP_ENTRIESv2 that would detect illegal characters in the
filename.
Apart from whether it's necessary, making the filename the last field would
simplify the code. Just .if defined(DESKTOP_ENTRIES) or
defined(DESKTOP_ENTRIESv2) at the start of parameter processing, and a .if
defined(DESKTOP_ENTRIESv2) section after it to override the filename. It
could also be made polymorphic, basing what it does on the number of fields
rather than a new DESKTOP_ENTRIESv2 define.
That was my first ideal, but since the entire processing is done in a
@set ${DESKTOP_ENTRIES{,v2}} XXX ; while [$$# -gt {6,7}]; do
filename=$${4,1}... ; done loop, I wasn't sure how to change this
part.
Scot
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
But then we would still need to add a check to check-desktop-entries for DESKTOP_ENTRIESv2 that would detect illegal characters in the filename. Since this is not user settable IMHO the check should really be done in portlint, not in b.p.m. -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
On 15 Jul 2011 03:16, Stephen Montgomery-Smith step...@missouri.edu wrote: On 07/14/2011 02:29 PM, Chris Rees wrote: On 14 Jul 2011 17:58, Stephen Montgomery-Smith step...@missouri.edu mailto:step...@missouri.edu wrote: Joe Average user who doesn't actually install the ports shouldn't be expected to read UPDATING. Er... he really should and is expected to. The situation I am thinking of is where a group all use FreeBSD. One person is responsible for installation and upkeep of the computers, and everyone else just uses them (for example, they don't have root access). An example of this is the University of Missouri Math Dept about 10 years ago. We all used FreeBSD. Now being Mathematicians, most of us didn't have a clue about how it all worked inside. Most of us wouldn't even understand what the UPDATING entries mean. Since then, most of the Dept have moved to Windows or the Mac. I am one of the few who still uses FreeBSD. So maybe you are correct after all - only use FreeBSD if you are a power user. No, I see your point now, and I'm sorry. I was surprised, because I wouldn't have expected you to say reading updating was mandatory! Now I realise that's not what you said. I'll return to my cave. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
Warren Block píše v pá 15. 07. 2011 v 07:15 -0600: It could also be made polymorphic, basing what it does on the number of fields rather than a new DESKTOP_ENTRIESv2 define. I believe that's impossible because you can create several desktop entries by repeating the quadruple of values in this variable. Quite similar to OPTIONS. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org ... the obese drugged penguin used by Linux. -- Scott Long signature.asc Description: This is a digitally signed message part
Re: What about creating an office team
On 15 July 2011 16:35, Philipp Ost p...@smo.de wrote: Baptiste Daroussin wrote: [...] maybe many more? (you can propose your candidate here :)) What about math/gnumeric? It's a nice, lightweight spreadsheet if one doesn't want the `bloat' that is open-/libreoffice. Good luck with your project! gnumeric is maintained by gnome@, CCd. I'd imagine they might want to hang on to it. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
On Fri, 15 Jul 2011, Pav Lucistnik wrote: Warren Block píše v pá 15. 07. 2011 v 07:15 -0600: It could also be made polymorphic, basing what it does on the number of fields rather than a new DESKTOP_ENTRIESv2 define. I believe that's impossible because you can create several desktop entries by repeating the quadruple of values in this variable. Quite similar to OPTIONS. It would be just like the error check at the start of the routine, look for an even multiple of 6 or 7 fields. But that brings up another problem. All desktop entries would have to be the same type. Can't set the filename for one and leave the others alone. Unless empty fields are used to mean a default filename, and that just makes it more complicated for a rare situation. FWIW, I think the original code with a better regex like Jung-uk Kim has in http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068737.html is still the way to go. If the port requires a special desktop entry filename, that seems beyond the scope of the DESKTOP_ENTRIES variable. This all should be documented in the Porter's Handbook, and I'll volunteer to work on the DESKTOP_ENTRIES section once there's a decision on the code.___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
On 07/15/2011 04:57 PM, Warren Block wrote: FWIW, I think the original code with a better regex like Jung-uk Kim has in http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068737.html is still the way to go. If the port requires a special desktop entry filename, that seems beyond the scope of the DESKTOP_ENTRIES variable. I agree. DESKTOP_ENTRIESv2 seems like a lot of work for just three ports. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [RFC] A trivial change for DESKTOP_ENTRIES (take 2)
On Fri, 15 Jul 2011, Stephen Montgomery-Smith wrote: On 07/15/2011 04:57 PM, Warren Block wrote: FWIW, I think the original code with a better regex like Jung-uk Kim has in http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068737.html is still the way to go. If the port requires a special desktop entry filename, that seems beyond the scope of the DESKTOP_ENTRIES variable. I agree. DESKTOP_ENTRIESv2 seems like a lot of work for just three ports. It's not even three ports. AFAIR, the only current port where it matters is x11-wm/compiz, the port that exposed the problem. Allowing dashes fixes that. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Submitting a follow up to a port update
Hi All, I'm the current maintainer for the scons port. http://www.freebsd.org/cgi/query-pr.cgi?pr=158205 As you can see, on the 24th June an update/patch was requested. I also received 2 emails, one from skreuzer via FreeBSD-gnats-submit and then also one from Edwin via bug-followup. So I check it out etc, looks fine and I want to approve it. So what did I do I clicked on the 'Submit Followup' link on the webpage (mailto:bug-follo...@freebsd.org,skreu...@freebsd.org?subject=Re:%20ports/15 8205:%20%5BPATCH%5D%20devel%2Fscons%3A%20update%20to%20%32.%30.%31) I send my email there and to 'bug-follo...@freebsd.org'; 'skreu...@freebsd.org' on the 25th June. Not only have I not heard anything but my follow up and approval to patch has not appeared on the patch [158205] I assume I have done something wrong? I also assume folks think I have been ignoring them and will get ousted by a maintainer timeout when in fact I replied approving the patch after only one day. What do I need to do now? Thanks Gav... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Submitting a follow up to a port update
On 12 July 2011 23:38, Gavin McDonald ga...@16degrees.com.au wrote: Hi All, I'm the current maintainer for the scons port. http://www.freebsd.org/cgi/query-pr.cgi?pr=158205 As you can see, on the 24th June an update/patch was requested. I also received 2 emails, one from skreuzer via FreeBSD-gnats-submit and then also one from Edwin via bug-followup. So I check it out etc, looks fine and I want to approve it. So what did I do I clicked on the 'Submit Followup' link on the webpage (mailto:bug-follo...@freebsd.org,skreu...@freebsd.org?subject=Re:%20ports/15 8205:%20%5BPATCH%5D%20devel%2Fscons%3A%20update%20to%20%32.%30.%31) I send my email there and to 'bug-follo...@freebsd.org'; 'skreu...@freebsd.org' on the 25th June. Not only have I not heard anything but my follow up and approval to patch has not appeared on the patch [158205] I assume I have done something wrong? I also assume folks think I have been ignoring them and will get ousted by a maintainer timeout when in fact I replied approving the patch after only one day. What do I need to do now? Thanks Gav... pgollucci@ has just fixed it for you. All you have to do is wait for skreuzer@ to commit it ;) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ports/144597: security/openssh-portable fails to compile with KERBEROS enabled
On 07/15/2011 06:28 PM, Stephen Montgomery-Smith wrote: On 07/15/2011 06:23 PM, Jason Hellenthal wrote: On Wed, Jul 13, 2011 at 11:39:01PM -0500, Stephen Montgomery-Smith wrote: Hey people, I was looking over old unresolved PR's. I came across this one: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/144597 When I sent a message to the submitter of the PR, the email bounced back suggesting that the submitter no longer uses that email address. I don't think it would be too hard to make the port build under the circumstances he describes. But is ANYONE interested? Would it be worth investing effort to make this work? Note that the port has ports@ as its maintainer, so it doesn't look like there is a lot of interest. Thanks, Stephen P.S. This one is related: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/57498 Is this a big bag of worms? I can see that seems to be fixed, for example, in mail/fetchmail. Considering that the port version is 5.2p1 and the current version in stable/8 is 5.4p1 and greater than that for HEAD I would say it would be much more of a benefit to get the port updated to the latest version and then work on it from there, otherwise its a loss of time for an outdated version. Last time I looked at this port it was a mess with a collection of third party patches from all over the place which I think lead to a discrepancy in the update of the port but that's just my opinion. It would be nice to see a simplified version of this port so it isn't such a monster to update and have an option for a user supplied patches directory that stands outside of the tree (user configured path) and it just blindly attempts to apply what is in that directory. I think this would help slim it down a little so it can consistently be bumped to a new revision without hassle. Something like: # Defaults to /usr/ports/patches unless path is user specified. WITH_PATCH_TREE?=/usr/ports/patches /usr/ports/patches/ # Distributed empty. everything else user created. |-- net | `-- wireshark `-- security |-- gnupg `-- openssh-portable Things like this would certainly make it easier for a consistent user supplied patch to be kept local for build machines. I can't count the times on 2 hands and 2 feet that I wanted to patch a port with a local patch and had to continuously cp(1) a patch back to a ports tree using rsync(1) All these are good ideas, but I am not the person to do it. I don't use this software. I'm going to relinquish responsibility for this PR. I found some possible maintainers of this port at http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/150493. If either of them reply, then I'll pick it up again. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
