Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
Doug Barton wrote: > On 09/02/2011 14:58, Lars Eighner wrote: > > The main thing here, of course, is that ports uses "dependency" > > in the exact opposite of its normal English sense (just as > > twitter uses "following" in the exact opposite of its normal > > English sense). > > > > In normal Engish 'X is a dependency of Y' means Y is necessary > > for X (X depends on Y) > > I'm not sure why you believe this to be true. Can you give > examples from non-technical English prose, and some dictionary > definitions to back up your claim? In normal English, I would not expect "dependency" to be used that way at all. Instead, I would expect something along the lines of "a state of dependency exists between X and Y". To specify the direction of the relationship, I would expect "X depends on Y" or, equivalently, "X is a dependent of Y" -- the latter being more often seen as "X is Y's dependent". Example: in connection with income taxes, "my son is my dependent". ___ 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: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
On 09/03/2011 07:09, per...@pluto.rain.com wrote: > In normal English, I would not expect hence my recommendation to go do some research. :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
On Fri, 2 Sep 2011, Doug Barton wrote: On 09/02/2011 14:58, Lars Eighner wrote: The main thing here, of course, is that ports uses "dependency" in the exact opposite of its normal English sense (just as twitter uses "following" in the exact opposite of its normal English sense). In normal English 'X is a dependency of Y' means Y is necessary for X (X depends on Y) I'm not sure why you believe this to be true. Because it is a fact. Can you give examples from non-technical English prose, and some dictionary definitions to back up your claim? I am a little hurt that my own authority does not suffice for both the New York Times Book Review and the Time Literary Supplement (that's in London, y'all) have remarked on my mastery of the English language. But much more than that, I am appalled at the state of education in this country that you do not immediately recognize for yourself that my point is correct, once I have made it. There are two senses of 'dependency' in normal English. One means 'the state of dependence, (MWCD11th expresses this as being a synonym for DEPENDENCE; this is the oldest sense in English because MWCD11th lists senses in historical order), and the other is something that is dependent on something else. Well, okay, there are three senses, as there is a relatively recent one meaning a small building (such as a stable, garage, or bike shed) adjacent to a larger one. Almost all of the examples I turn up from grepping my corpus relate to international relations except for the most recent entries where it is bound to 'Chemical.' Well, 'chemical dependency' is perfectly common modern English and of course it does not mean the chemical depends on the user, but just the opposite. So in normal English, if I write myperlscript.pl, it is a dependency of perl. My script cannot run without perl, but perl can go on happily without my script. Perl does not depend on my script, so it is not the dependency. My script does depend on perl, so my script is the dependency. The correct word for what computer people call a dependency is 'requisite.' Perl is a requisite of my script. My script is a dependency of perl. Why is there such a thing as emacs cramp? Because the person who wrote it considered himself such a genius that he did not have to think of ergonomics and so bound just about everything to ^X and ^C and combinations thereof (and subsequent geniuses have made the possibly of remapping merely theoretical). Why are most editors and word processors just about unusable (out of the box) for writers? Because programmers are such geniuses, the idea of consulting working writers before they begin such a project seems laughable to them. And that is why ports uses 'dependency' exactly backwards -- the authors are such geniuses that they cannot be bothered to open a dictionary for themselves. I can think of a case in point. Now it is possible that once upon a time there was a programmer who knew what dependency meant, and he might have said something like "My script has a dependency on perl." That is accurate, but very awkward compared with "Perl is a requisite of my script." And perhaps that awkward expression was passed around among the programmerlings, as in the game gossip, until it became "Perl is a dependency of my script," which is dead wrong, so if my script is a port, and perl is missing, the report "stale dependency" is entirely misleading. My script is the dependency. It is not stale. It is missing its requisite, namely perl. It is a constant source of confusion for native speakers of English, and to a degree a source of amusement that documentation which has not yet been expressed in correct English is being translated into dozens of languages which take up space in machines that accept the default install. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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 system quality
On Fri, Sep 02, 2011 at 11:49:48AM +0200, Julian H. Stacey wrote:
> Hi,
> Reference:
> > From: "Julian H. Stacey"
> > Date: Fri, 02 Sep 2011 03:07:40 +0200
> > Message-id: <201109020107.p8217efj089...@fire.js.berklix.net>
>
> I wrote:
> > Microsoft must grin at all us BSD, Linux, maybe Solaris & presumably
> > even now http://www.minix3.org free source enthusiasts reinventing
> > similar old ports shims for same old 3rd party wheels:.
>
> FYI:
> http://www.minix3.org ->
> http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages ->
> http://pkgin.net/
> "
> pkgin is known to work and have been tested under the following platforms :
> * NetBSD 4.0
> * NetBSD 5.{0,1}
> * NetBSD current
> * DragonFly BSD 2.0 to 2.8
> * DragonFly BSD current
> * Solaris 10/SunOS 5.10
> * Opensolaris/SunOS 5.11
> * Debian GNU/Linux 5.0
> * Mac OS X 10.{5,6}
> * MINIX 3.1.8
> "
>
> No /pub/FreeBSD/branches/-current/ports/ports-mgmt/pkgin .
> I'm not familiar with pkgin, but nice to see OS co-operation.
>
> Cheers,
> Julian
pkgin is mostly driven by a single person, I really know well pkgin, because I
ported it to FreeBSD in the past. There are patches from Minix and Dragonfly
users, but through mostly things are done by the original author, and to help
portability but no much.
I have picked up some ideas from pkgin for pkgng and the last version of pkgin
picked up some idea from pkgng. (Me and Emile Heitor - the author of pkgin -
discuss and share ideas quite often about pkgin and pkgng)
regards,
Bapt
pgprzT70NAnyw.pgp
Description: PGP signature
Re: Ports system quality
On Fri, Sep 02, 2011 at 12:04:01PM +0200, Kurt Jaeger wrote: > Hi! > > > > http://pkgin.net/ > [...] > > > pkgin is known to work and have been tested under the following platforms > [...] > > So, what do you actually mean by this? > > Probably just this: What about trying to port pkgin for FreeBSD, so that > pkgin can also be used on FreeBSD ? > > If this solves the binary pkg-install problem in a generic > way on many plattforms (I have not looked at the implementation), > that might be a nice feature. > As I said I have done this, but finally went to pkgng because of some problem (version scheme between pkgsrc and freebsd differs) and other things. regards, Bapt pgplDLrLFeuYM.pgp Description: PGP signature
Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/03/2011 01:56 AM, Lars Eighner wrote: > On Fri, 2 Sep 2011, Doug Barton wrote: > >> On 09/02/2011 14:58, Lars Eighner wrote: > >>> The main thing here, of course, is that ports uses "dependency" in >>> the >>> exact opposite of its normal English sense (just as twitter uses >>> "following" in the exact opposite of its normal English sense). >>> >>> In normal English 'X is a dependency of Y' means Y is necessary >>> for X (X >>> depends on Y) >> >> I'm not sure why you believe this to be true. > > Because it is a fact. > >> Can you give examples from non-technical English prose, and some >> dictionary definitions to back up your claim? > > I am a little hurt that my own authority does not suffice for both > the New > York Times Book Review and the Time Literary Supplement (that's in > London, > y'all) have remarked on my mastery of the English language. But > much more > than that, I am appalled at the state of education in this country > that you > do not immediately recognize for yourself that my point is correct, > once I > have made it. > > There are two senses of 'dependency' in normal English. One means > 'the state > of dependence, (MWCD11th expresses this as being a synonym for > DEPENDENCE; > this is the oldest sense in English because MWCD11th lists senses in > historical order), and the other is something that is dependent on > something > else. Well, okay, there are three senses, as there is a relatively > recent > one meaning a small building (such as a stable, garage, or bike shed) > adjacent to a larger one. > > Almost all of the examples I turn up from grepping my corpus relate to > international relations except for the most recent entries where it > is bound > to 'Chemical.' Well, 'chemical dependency' is perfectly common modern > English and of course it does not mean the chemical depends on the > user, but > just the opposite. > > So in normal English, if I write myperlscript.pl, it is a dependency of > perl. My script cannot run without perl, but perl can go on happily > without > my script. Perl does not depend on my script, so it is not the > dependency. My script does depend on perl, so my script is the > dependency. > > The correct word for what computer people call a dependency is > 'requisite.' > Perl is a requisite of my script. My script is a dependency of perl. > > Why is there such a thing as emacs cramp? Because the person who > wrote it > considered himself such a genius that he did not have to think of > ergonomics > and so bound just about everything to ^X and ^C and combinations > thereof > (and subsequent geniuses have made the possibly of remapping merely > theoretical). Why are most editors and word processors just about > unusable > (out of the box) for writers? Because programmers are such > geniuses, the > idea of consulting working writers before they begin such a project > seems > laughable to them. > > And that is why ports uses 'dependency' exactly backwards -- the > authors are > such geniuses that they cannot be bothered to open a dictionary for > themselves. I can think of a case in point. > > Now it is possible that once upon a time there was a programmer who > knew > what dependency meant, and he might have said something like "My > script has > a dependency on perl." That is accurate, but very awkward compared > with > "Perl is a requisite of my script." And perhaps that awkward > expression was > passed around among the programmerlings, as in the game gossip, > until it > became "Perl is a dependency of my script," which is dead wrong, so if > my script is a port, and perl is missing, the report "stale > dependency" is > entirely misleading. My script is the dependency. It is not > stale. It is > missing its requisite, namely perl. > > It is a constant source of confusion for native speakers of English, > and to > a degree a source of amusement that documentation which has not yet > been > expressed in correct English is being translated into dozens of > languages > which take up space in machines that accept the default install. > One of the best most unnecessary replies to something unneeded I've read in a long, LONG time. Well done, sir! (It's a keeper!) - -Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5h4DoACgkQGK3MsUbJZn6q3QCePhBtBbUfd90ORira5YuZ+OYu F5oAnjzHraki17HKOccoOB4rUCly+g5D =CNIG -END PGP SIGNATURE- ___ 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: Compiling for gtk3
On 3-9-2011 8:28, Conrad J. Sabatier wrote: I've been trying to compile pan2 from the master git repository, and am having problems getting a build that will actually run using the --with-gtk3 configure switch. The compilation goes OK, but execution fails with... [conrads@serene ~/build/pan2]$ pan/gui/pan Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported aborting... Abort trap: 6 (core dumped) You will need to disable gtkspell. You can't mix GTK+ 2 and GTK+ 3 widgets in the same application. Since gtkspell is a GTK+ 2 library and pan is a GTK+ 3 apps. -Koop What's the key to getting an app to work with gtk3? Obviously, I'm missing something here. Thanks. ___ 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: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
Am 03.09.2011 09:56, schrieb Lars Eighner: > The correct word for what computer people call a dependency is 'requisite.' > Perl is a requisite of my script. My script is a dependency of perl. > ... > Because programmers are such geniuses, the > idea of consulting working writers before they begin such a project seems > laughable to them. > > And that is why ports uses 'dependency' exactly backwards -- the authors > are > such geniuses that they cannot be bothered to open a dictionary for > themselves. I can think of a case in point. > > Now it is possible that once upon a time there was a programmer who knew > what dependency meant, and he might have said something like "My script has > a dependency on perl." That is accurate, but very awkward compared with > "Perl is a requisite of my script." And perhaps that awkward expression was Being a non-native speaker, I am nonetheless aware of the difference between the rather noun-oriented style of my own native tongue, German, and the rather verb-oriented style of English. So, that latter quoted phrase of yours could be rewritten as "My script requires Perl", and one step further, "My script needs Perl" (not sure if you want to go that last step). It's clear, there is no passive voice, the sentence starts with the familiar, namely the script at the user's hand, does not need a cumbersome of-possessive construct. > It is a constant source of confusion for native speakers of English, and to > a degree a source of amusement that documentation which has not yet been > expressed in correct English is being translated into dozens of languages > which take up space in machines that accept the default install. It is not only a source of confusion for native speakers, but also to non-native speakers. I'd support a motion to replace "dependency" by "requisite" in port and package management tools to remove the ambiguity. ___ 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 system quality
Baptiste Daroussin wrote:
> On Fri, Sep 02, 2011 at 11:49:48AM +0200, Julian H. Stacey wrote:
> > Hi,
> > Reference:
> > > From: "Julian H. Stacey" =20
> > > Date: Fri, 02 Sep 2011 03:07:40 +0200=20
> > > Message-id: <201109020107.p8217efj089...@fire.js.berklix.net>=20
> >=20
> > I wrote:
> > > Microsoft must grin at all us BSD, Linux, maybe Solaris & presumably
> > > even now http://www.minix3.org free source enthusiasts reinventing
> > > similar old ports shims for same old 3rd party wheels:.=20
> >=20
> > FYI:
> > http://www.minix3.org ->
> > http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages ->
> > http://pkgin.net/
> > "
> > pkgin is known to work and have been tested under the following platforms=
> :
> > * NetBSD 4.0
> > * NetBSD 5.{0,1}
> > * NetBSD current
> > * DragonFly BSD 2.0 to 2.8
> > * DragonFly BSD current
> > * Solaris 10/SunOS 5.10
> > * Opensolaris/SunOS 5.11
> > * Debian GNU/Linux 5.0
> > * Mac OS X 10.{5,6}
> > * MINIX 3.1.8
> > "
> >=20
> > No /pub/FreeBSD/branches/-current/ports/ports-mgmt/pkgin .
> > I'm not familiar with pkgin, but nice to see OS co-operation.
> >=20
> > Cheers,
> > Julian
>
> pkgin is mostly driven by a single person, I really know well pkgin, becaus=
> e I
> ported it to FreeBSD in the past. There are patches from Minix and Dragonfly
> users, but through mostly things are done by the original author, and to he=
> lp
> portability but no much.
> I have picked up some ideas from pkgin for pkgng and the last version of pk=
> gin
> picked up some idea from pkgng. (Me and Emile Heitor - the author of pkgin -
> discuss and share ideas quite often about pkgin and pkgng)
>
> regards,
> Bapt
OK :-)
Suggestion: If He make some note about FreeBSD/pkgng on his page would help,
you could both cross link a See Also type href.
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Reply below, not above; Indent with "> "; Cumulative like a play script.
Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct.
___
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: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
Hello, On Sat, Sep 3, 2011 at 9:56 AM, Lars Eighner wrote: > I am a little hurt that my own authority does not suffice for both the New > York Times Book Review and the Time Literary Supplement (that's in London, > y'all) have remarked on my mastery of the English language. But much more > than that, I am appalled at the state of education in this country that you > do not immediately recognize for yourself that my point is correct, once I > have made it. Congratulations on being recommended (applauded? I'm sorry, but I am a non-native user of the English language). > The correct word for what computer people call a dependency is 'requisite.' > Perl is a requisite of my script. My script is a dependency of perl. If somebody decides to "fix" the language of these tools (or any tools for that matter), they should keep in mind that many users are non-native speakers of the English language. Correct English is good, but but plain, simple and common English is better. No uncommon words please. -- Regards, Torfinn Ingolfsen ___ 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: editors/zim
oops not sent to list... On 03/09/2011 00:34, Glen Barber wrote: Hi Chris, On 9/2/11 5:40 PM, Chris Whitehouse wrote: did you see that I had to add a line for MD5 to distinfo to make it work on my 8.1-R system? Though the last change was to remove MD5... It sounds to me parts of your ports tree may be out of sync. MD5 distfile validation was removed from ports some time ago. You're right in a sense. It's ports from late 2010 with the new port of zim which I've added manually. I didn't realise MD5 had been removed. Chris How do you update your ports tree? Regards, Glen ___ 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: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
On Sat, 3 Sep 2011, Torfinn Ingolfsen wrote: The correct word for what computer people call a dependency is 'requisite.' Perl is a requisite of my script. My script is a dependency of perl. If somebody decides to "fix" the language of these tools (or any tools for that matter), they should keep in mind that many users are non-native speakers of the English language. Correct English is good, but but plain, simple and common English is better. No uncommon words please. Curiously enough, the man page for portupgrade begins by defining "required" and "dependent" accurately. These are adjectives, but a step in the right direction. "Requirement" might do better than "requisite." Unfortunately, the messages emitted by parts of the portupgrade package do not achieve a similar level of clarity. For example, in certain circumstances, portuprade says "Gathering depends." "Depends" is a verb (and now a proprietary name for adult diapers) -- it does not have a sense as a common noun. I understand why such abbreviated messages may be useful in programming and debugging. But it does not belong in the production copy. Either it should be meaningful to the user or it should be eliminated. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266___ 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"
x11-toolkits/tk84 install can't stat: /usr/local/man/man3/3DBorder.3
Hi I see this error (on current too) cd /usr/ports/x11-toolkits/tk84 printenv PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin TERM=xterm PWD=/usr/ports uname -a FreeBSD blak.js.berklix.net 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu May 19 13:49:29 CEST 2011 j...@blak.js.berklix.net:/ad6s4/release/8.2-RELEASE/src/sys/amd64/compile/BLAK.small amd64 Variants of: make clean ; make install make clean ; make WITH_TK84_DOC=YES FORCE_PKG_REGISTER=YES reinstall always bomb with: . install -o root -g wheel -m 444 /ad6s4/release/8.2-RELEASE/ports/x11-toolkits/tk84/work/tk8.4.19/unix/../doc/wish.1 /usr/local/man/man1/wish8.4.1 ===> Compressing manual pages for tk-8.4.19_2,2 gzip: can't stat: /usr/local/man/man3/3DBorder.3: No such file or directory gzip: can't stat: /usr/local/man/man3/AddOption.3: No such file or directory gzip: can't stat: /usr/local/man/man3/BindTable.3: No such file or directory ... ober 100 lines deleted. gzip: can't stat: /usr/local/man/mann/wm.n: No such file or directory ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib ===> Registering installation for tk-8.4.19_2,2 Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. ___ 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: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
Torfinn Ingolfsen wrote: > ... but I am a > non-native user of the English language). ... > Correct English is good, but but plain, simple and common English is better. Yes :-) (I'm native English, but in Germany). I also believe shorter sentences work better (in either language). Easy to forget though, as local societies condition us to use more complex grammar for written than verbal communication. Those with the most complex articulation mostly win top professional status / income. > No uncommon words please. Yes, except eg "NEED =" as a Makefile key word would be too short, with false matches with find & grep, "RUN_DEPENDS" & "BUILD_DEPENDS" OK. "REQUISITE" some natives would mis-spell. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. ___ 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: x11-toolkits/tk84 install can't stat: /usr/local/man/man3/3DBorder.3
Julian H. Stacey wrote on 03.09.2011 15:38:
Hi
I see this error (on current too)
cd /usr/ports/x11-toolkits/tk84
printenv
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin
TERM=xterm
PWD=/usr/ports
uname -a
FreeBSD blak.js.berklix.net 8.2-RELEASE FreeBSD 8.2-RELEASE
#0: Thu May 19 13:49:29 CEST 2011
j...@blak.js.berklix.net:/ad6s4/release/8.2-RELEASE/src/sys/amd64/compile/BLAK.small
amd64
Variants of:
make clean ; make install
make clean ; make WITH_TK84_DOC=YES FORCE_PKG_REGISTER=YES reinstall
always bomb with:
.
install -o root -g wheel -m 444
/ad6s4/release/8.2-RELEASE/ports/x11-toolkits/tk84/work/tk8.4.19/unix/../doc/wish.1
/usr/local/man/man1/wish8.4.1
===>Compressing manual pages for tk-8.4.19_2,2
gzip: can't stat: /usr/local/man/man3/3DBorder.3: No such file or directory
gzip: can't stat: /usr/local/man/man3/AddOption.3: No such file or directory
gzip: can't stat: /usr/local/man/man3/BindTable.3: No such file or directory
... ober 100 lines deleted.
gzip: can't stat: /usr/local/man/mann/wm.n: No such file or directory
===>Running ldconfig
/sbin/ldconfig -m /usr/local/lib
===>Registering installation for tk-8.4.19_2,2
Cheers,
Julian
I can reproduce this behavior with TK84_DOC is on (default off).
The problem is that this port doesn't actually install man-pages from
${MAN3} and ${MANN}, so this option is bogus.
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
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: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
On Sat, Sep 3, 2011 at 3:39 AM, Lars Eighner wrote: > On Sat, 3 Sep 2011, Torfinn Ingolfsen wrote: > > The correct word for what computer people call a dependency is >>> 'requisite.' >>> Perl is a requisite of my script. My script is a dependency of perl. >>> >> >> If somebody decides to "fix" the language of these tools (or any tools >> for that matter), they should keep in mind that many users are >> non-native speakers of the English language. >> Correct English is good, but but plain, simple and common English is >> better. >> No uncommon words please. >> > > Curiously enough, the man page for portupgrade begins by defining > "required" > and "dependent" accurately. These are adjectives, but a step in the right > direction. "Requirement" might do better than "requisite." > I suggested that verbiage, and I'm Dutch. http://cvsup.hu.freebsd.org/viewvc/FreeBSD/ports/ports-mgmt/portupgrade/distinfo?sortby=log&view=log > -- Jos Backus jos at catnook.com ___ 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: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation
On Sat, Sep 03, 2011 at 11:26:07AM +0200, Matthias Andree wrote: > > I'd support a motion to replace "dependency" by "requisite" in port and > package management tools to remove the ambiguity. I think that's a terrible idea. If we are going to change the terms used for such things, we should angle more toward an E-Prime approach to phrasing in such cases. Don't misunderstand -- I think that trying to write or speak in E-Prime all the time is an even worse idea. There are contexts where it's a great idea, though, and this is one of them. Using terms like "dependency" and "requisite" in this context tends toward tortuous sentence construction and other Byzantine absurdities. If we're going to change the phrasing, go with this like "Foo depends on bar," and "Bar requires foo." Aruing over whether it should be "Foo is a dependency of bar," or "Foo is a requisite of bar," utterly misses the most important point here: both of them suck. By the way, "dependency" in simplest terms just means that the thing in question is dependent or subordinate upon something else. That, to me, means that "stale dependency" says the dependency information for the dependent port is stale. That doesn't sound wrong at all. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgp5DoKdriHyC.pgp Description: PGP signature
portsnap: one metadata file is corrupted
Hi there, Could anyone explain why this may happen and what should I do? My system is 7.4-STABLE, built from today's sources. Thank you. mercury# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. Fetching snapshot tag from portsnap5.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Wed Oct 13 17:09:57 IST 2010 to Sat Sep 3 20:15:14 IDT 2011. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 4 metadata files... gunzip: (stdin): unexpected end of file metadata is corrupt. mercury# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. Fetching snapshot tag from portsnap6.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Wed Oct 13 17:09:57 IST 2010 to Sat Sep 3 20:25:27 IDT 2011. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... gunzip: (stdin): unexpected end of file metadata is corrupt. mercury# ___ 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"
INDEX-9
In light of the upcoming release of 9.0-RELEASE it might be a good idea to start providing INDEX-9 via portsnap. Especially since we want people to try the BETA releases. Thoughts? Emanuel ___ 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: tinderbox: how to drop unneded Jail and Build
Chris Rees wrote on 25.08.2011 19:52:
On 25 August 2011 14:27, Ruslan Mahmatkhanov wrote:
Chris Rees wrote on 25.08.2011 16:51:
On 25 August 2011 13:44, Ruslan Mahmatkhanovwrote:
How to correctly remove Jail and Build, created by ./tc createJail and
./tc
createBuild accordingly? I have 7.3-FreeBSD, that was needed to one-time
test single port. As far i understand, it's not enough to remove
directory
${pb}/7.3-FreeBSD, since there is logs/packages/build
etc for this build and database records also. How to deal with this
correctly?
cd ${pb}/scripts&&./tc rmBuild -b ${build}&&./tc rmJail -j ${jail}
rm -r ${pb}/*/${jail_name} ${pb}/*/${build_name} ${pb}/${build_name}
PLEASE check the globbing using echo first
You may want to join tinderbox-l...@marcuscom.com too ;)
Chris
Nice, thank you. I believe that this should be added to the Tinderbox
Manual. And what about creating 9.0-BETA1 jail with -u LFTP question?
I've added it to the README, thanks for the suggestion [1].
By the way, i believe that README.html#CHINSTALLATION
should be updated (or added as option) with -u CSUP instead of -u CVSUP
there in step 12:
# cd ${pb}/scripts && ./tc createJail -j 8.2 -d "FreeBSD 8.2-RELEASE" \
-t RELENG_8_2_0_RELEASE -u CVSUP
Since csup is now available in all supported FreeBSD versions. May be
add example for -CURRENT too.
For now I think you need to use csup and make world method for 9-,
sorry. I'm talking to re about what the future plans are regarding ftp
-- not sure if this xz distribution is The Future.
Chris
[1] http://marcuscom.com/pipermail/tinderbox-cvs/2011-August/001527.html
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
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: INDEX-9
On 09/03/11 12:41, Emanuel Haupt wrote: In light of the upcoming release of 9.0-RELEASE it might be a good idea to start providing INDEX-9 via portsnap. Especially since we want people to try the BETA releases. Yes, this will happen soon. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ 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: Why do we not mark vulnerable ports DEPRECATED?
Several people have pointed out something I omitted from my first post
on this, if you have portaudit installed you're already prevented from
installing a vulnerable port:
# make
===> mediawiki-1.15.5_2 has known vulnerabilities:
=> mediawiki -- multiple vulnerabilities.
Reference:
http://portaudit.FreeBSD.org/3fadb7c6-7b0a-11e0-89b4-001ec9578670.html
=> Please update your ports tree and try again.
*** Error code 1
So all I'm talking about doing is extending the same protection to *all*
of our users without requiring them to install portaudit and keep it up
to date.
More below ...
On 08/29/2011 23:25, Mark Linimon wrote:
> On Mon, Aug 29, 2011 at 10:48:31PM -0700, Doug Barton wrote:
>> Can someone explain why this would be a bad idea?
>
> Very early in my committer career, I marked a port BROKEN that kde
> depended on. I was quickly chastisted by people trying to install kde :-)
>
> So, the right answer may be "it depends". For unmaintained leaf or
> leaf-ish ports like you're talking about, I think the answer is exactly
> correct -- such ports do nothing but cause users problems. But I think
> it would be counterproductive to mark e.g. php5 and firefox as such
> whenever a new vulnerability is found. It's just simply too common* an
> occurrence.
We'll have to agree to disagree on the timing issue here. Having talked
this through on IRC quite a bit and read the responses to this thread I
still think that (absent an update that clears the vulnerability) we
should be marking them FORBIDDEN (note, you were kind enough to correct
me on this point on IRC, thanks) immediately, and not clear that until
the port is updated.
This would serve several beneficial purposes, in no particular order:
1. It would solve the problem of us forgetting to do it later.
2. It would help prevent users who do not have portaudit installed (or
have it installed but have not updated recently) from installing
vulnerable stuff.
3. It would facilitate removal of vulnerable stuff down the road.
4. The more popular the port, the more likely resources will appear to
get it fixed if people who want it cannot install it.
Meanwhile, I got bit by this problem AGAIN, so I decided to put my money
where my mouth is. I did a search of the INDEX ('portaudit -f
/usr/ports/INDEX-9') and came up with 54 ports that are in the tree and
vulnerable. Of those, 10 are maintained by ports@, so I've marked those
all FORBIDDEN, with EXPIRATION_DATE of 2011-09-30. Many of those ports
have been vulnerable for years, the oldest since 2005-07-31. One of
those was fixed within an hour after my marking it FORBIDDEN. :)
For the other 44 I sent e-mail to the maintainers asking them to take
action and letting them know about my plan to mark the ports FORBIDDEN
this time next week. Two maintainers (out of the 33 unique non-ports@
maintainers) have already responded. Overall I'd say that the response
to this idea has been very positive.
If we all cannot agree that marking them FORBIDDEN immediately is a good
idea, can we at least agree on a guideline for when to mark newly
vulnerable ports? Y'all know my vote, but if "immediately" cannot
achieve consensus, what do people think is reasonable?
> A different but related topic: I don't think we've been sufficiently
> rigorous about marking DEPRECATED or BROKEN ports with EXPIRATION_DATEs.
> That could be a Junior Committer Task. (I know that Pav has swept some
> out in the past.)
Well I'm as junior as anyone, and in an axe-swinging mood lately, so I
took a look at this. The numbers for BROKEN-without-EXPIRATION_DATE are
large'ish, and given how BROKEN is being used in some of those ports it
wasn't immediately clear to me that setting EXPIRATION_DATE was the
right thing to do, so I left those alone. So if someone else wants to
tackle that one, go for it! :)
The number of DEPRECATED-without-EXPIRATION_DATEs on the other hand was
more manageable, and understandable even by me, so I have taken care of
these. There were 8 that have been deprecated for a long time, were
clearly hopeless cases, and were not depended on; so those I just
removed. Everything else I set EXPIRATION_DATEs for, and in some cases
also added DEPRECATED and EXPIRATION_DATE for things that depend on the
previously-deprecated ports. So, 2011-09-30 is going to be a fun day.
BWAHAHAHAHA
The only exception to the above are the lang/gcc[34]4 ports. Gerald
seems to have that situation well in hand, and since the intricacies
there were not immediately obvious to me I decided to leave well enough
alone.
hth,
Doug
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-u
Re: [ANNOUNCE]: clang compiling ports, take 2
On Mon, 25 Jul 2011, Matthias Andree wrote: > Namely: if a port sets USE_GCC=4.2+ (for instance, sysutils/busybox does > that), the Pointyhat build does not install GCC. I think the bug is in > ports/Mk/bsd.gcc.mk which is unaware that there are newer clang-based > 9-CURRENT systems without gcc. > > I hope we can have another -exp run soon that addresses this. Matthias, sorry for not getting to this earlier. If you look at Mk/bsd.port.mk, there is a line GCCVERSION_040200= 700042 99 4.2 which indicates that GCC 4.2 has been in the base system starting with FreeBSD 7.0 (and that magic 42 marker) until the rest of times. Can you advise which value of __FreeBSD_version to use? The official list at http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html does not have a reference from what I can see. Gerald ___ 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: [ANNOUNCE]: clang compiling ports, take 2
Roman Divacky wrote on 25.07.2011 19:59: Hi! Flz@ just run another exp-build with CC=clang and CXX=clang++. The results can be seen here: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/ Since the last run we've managed to fix the biggest offenders but that uncovered others that need fixing. The "Reason" column was extended and now shows "assumes_gcc" which is the lowest hanging fruit :) A lot of these failures are trivial to fix (ie. assumes_gcc reason) and prevent a lot of other ports from building. It would be great if you could skim over the list to see if some of the ports you maintain are broken and possibly try to fix them. A small introduction into the Clang+Ports can be read at: http://wiki.freebsd.org/PortsAndClang. Please focus on the biggest offenders (ie. ports that prevent the most other ports from building). Thank you for helping us again! Roman Divacky Hi, i maintain port (sysutils/rdup) that is failing with clang: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/rdup-1.1.11_1.log But it's hard to realize to me how to fix this. I've tried irc (#freebsd-clang and #freebsd-ports on irc.oftc.net) - and nobody hangs there. Can please anybody help? -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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"
