Re: Ion3 removal (Re: Ion3 license violation)
On Thu, Dec 13, 2007 at 07:43:36AM +, Tuomo Valkonen wrote: On 2007-12-13, Mark Linimon [EMAIL PROTECTED] wrote: Further, note that my initial commit tried to do this, and I asked the author if it was acceptable. It was clear from his reply that it was not -- especially considering the following history: It seemed acceptable wrt. the source package; I was querying the effect on binary packages. It would have prevented binary packages. Also read again what I have written about the Xinerama module. Why is it not a separate package? What is it disguised as part of Ion, when it is not? ion-3 is deleted -- both in source form, and in binary package form -- so the point is moot. Even without the Xinerama code, I don't see how we could have met your 'no modifications' clause and still have ion-3 be able to run on FreeBSD. In fact, I don't see how any packaging system can meet that standard. Perhaps you can tell me where I'm wrong here. My conclusions from your interactions with Debian + Gentoo + ArchLinux + pkgsrc + OpenBSD is that it is not possible for us to meet your objections in a timely fashion for this release. Apparently only Debian felt like they could meet your objections, even in absence of a deadline; the others either deleted it, or, in the case of OpenBSD, stayed with an older version that predates these licensing clauses. I haven't investigated the state of ion-3 with respect to any other major Linux distributions; the above seem to me to be a representative enough sample. Of course, I'm puzzled why the deletion of ion-3 wasn't enough to end this discussion. I myself have no further interest in discussing it. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
On 2007-12-13, Mark Linimon [EMAIL PROTECTED] wrote: Even without the Xinerama code, I don't see how we could have met your 'no modifications' clause and still have ion-3 be able to run on FreeBSD. In fact, I don't see how any packaging system can meet that standard. Perhaps you can tell me where I'm wrong here. RTFLicense (which few seem to have done, and still moan about it). It talks about significant changes. If the name Ion(tm) or other names that can be associated with the Ion project are used to distribute this software, then: - A version that does not significantly differ from one of the copyright holder's releases, must be provided by default. In the explanations section: Significant change: Bug fixes are a priori insignificant as additions. Basic changes that are needed to install or run the software on a target platform are a priori insignificant. Additionally, basic configuration changes to better integrate the software with the target platform, without obstructing the standard behaviour, are a priori insignificant. Everything else is significant. The copyright holder reserves the right to refine the definition of significant changes on a per-case basis. Please consult when in doubt. -- Tuomo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
serious error possibly related to bsd.*.mk
Anybody else seeing this ? Seems to be pretty serious if it's not my
local issue.
$ portupgrade graphviz
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
This is after portsnap five minutes before this writing.
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 license violation
On Wed, Dec 12, 2007 at 07:59:34PM +, Tuomo Valkonen wrote: On 2007-12-12, Bill Moran [EMAIL PROTECTED] wrote: It's impossible for the FreeBSD ports system to guarantee compliance with his arbitrarily chosen 28 days rule. There is no 28 days rule. There is a latest release in 28 days or prominently mark (potentially) obsolete rule. I'm not sure how me as an end user not bothering to update my installed package for several months differs from me as a package distributor failing to update a binary distribution to your latest release within 28 days, If your intent is to stop people potentially running superceded code then maybe _you_ need to take some responsibility for this. If you bother to look at the top of your Xorg log, you will find something like the following (older versions of XFree86 included explicit dates for validity). Maybe you should do something similar. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-BETA2 i386 Current Operating System: FreeBSD ... Build Date: 04 November 2007 09:16:33PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. You can make the marking permanent, always requiring users to acknowledge a message. You can make the marking automatic, by checking the website for a new release (as Debian presently does), or by some more sophisticated means or dead man triggers. Feel free to submit patches. You may not be able to distribute such binary packages with your present setup, but source should be enough. In general, FreeBSD only distributes third-party packages in binary format. You may even simply have the package download and install http://iki.fi/tuomov/dl/ion-3-latest.tar.gz How will this work if the end user does not have web access or doesn't have the resources or desire to compile it? (signature in http://iki.fi/tuomov/dl/ion-3-latest.tar.gz.asc). This signature was created using a self-signed key and is therefore useless as a mechanism to verify the associated package. There is no way to verify that the person who created that signature is the same person who wrote the e-mail I am responding to or that either are actually the author of the official version of Ion-3. not about the days. The greatest difficulty to complying with the license are the idealist blockages in your head. You are free to use whatever license you desire for software that you write. The harder your license is to comply with, the less likely it is that people will comply with it - either they will ignore the license or they will not use the software. The FreeBSD Project takes license issues seriously and, since you refused to assist the Project in complying with your license, the Project had no alternative but to remove your software. I'd suggest that you are the one with the idealist blockages in your head. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpnYQVQUCKP0.pgp Description: PGP signature
Re: Ion3 license violation
On Thu, Dec 13, 2007 at 02:48:07AM -0800, Jeremy Chadwick wrote: I believe Mark removed the source tarball from the master FreeBSD FTP server, and very likely removed the binary packages as well. Correct. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 license violation
On 2007-12-13, Philip Paeps [EMAIL PROTECTED] wrote: I have not gone awol. I replied to your email about the port being out of date the day after you sent it. Closer to two days... It is not particularly difficult to comply with the licence. It just takes a bit of time (which I'm happy to spend) to keep up with new releases. Of course, sometimes new releases will coincide with ports freezes. This time the thaw came quite in time (or did I cause it?-), and maybe the period could have been even a bit longer if people would communicate about such things. However, there's still the problem of binary packages ending up in the release snapshots without prominent notices of obsoleteness. I don't think RCs and development snapshots should end up there at all. That's the problem with distros' megafreezes: you can't sync the development of thousands of packages. And as for stable releases, even they should get bugfixes promptly. Maybe the 28 day limit can be relaxed in such cases a bit, but even half a year may be too long -- two years like with Debian is certainly too long. It depends on the bug at hand: segfaults should be fixed very promptly, whereas minor glitches are not that big deal. -- Tuomo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
Tuomo Valkonen wrote: On 2007-12-12, Danny Pansters [EMAIL PROTECTED] wrote: The guy was never trying to find any compromise. What compromise can be had, when the distros never try to be constructive? Given that as your perspective (which you are of course entitled to), and given that we've already removed the software from our ports tree, I think it's probably reasonable at this point to let this thread die. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 license violation
On 2007-12-13, Jeremy Chadwick [EMAIL PROTECTED] wrote: Does this help you understand things a bit better? I know how the system works. I've even tried using FreeBSD on a couple of occasions -- and every time dependencies among the source packages have been broken, etc. -- Tuomo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 license violation
On Thu, Dec 13, 2007 at 11:42:53AM +0100, Philip Paeps wrote: Anyway. How does portmgr feel about this? Aye or nay? I do not yet believe that it is possible to meet Tuomo's interpretation of his license without his prior review of every possible patch, and I'm not willing to obligate the FreeBSD project, in perpetuity, to be able to do so. I have no faith whatsoever that the criteria won't change underneath us, based on the conversations with the pkgsrc, OpenBSD, and other package folks (as archived on public lists). Without written assurance from Tuomo that it won't, I cannot in good faith allow this code back in. I highly doubt that that will happen. The only situation I _might_ find acceptable is for us to follow OpenBSD's path and reintegrate the last release of ion-3 that was GPL only, without the extra clauses. Otherwise, I believe we are simply risking too much. Even that, however, I think is extremely risky, given his track record. From everything I've seen, the goalposts keep moving. I do not trust that they will not continue to do so. Therefore, I don't want to find out, in a court of law, which parts of this license are legally enforceable. It's simply not worth the trouble for one single package out of nearly 18,000. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 license violation
On 2007-12-13 10:54:47 (+), Tuomo Valkonen [EMAIL PROTECTED] wrote: On 2007-12-13, Philip Paeps [EMAIL PROTECTED] wrote: I have not gone awol. I replied to your email about the port being out of date the day after you sent it. Closer to two days... Yes. It is not particularly difficult to comply with the licence. It just takes a bit of time (which I'm happy to spend) to keep up with new releases. Of course, sometimes new releases will coincide with ports freezes. This time the thaw came quite in time (or did I cause it?-), and maybe the period could have been even a bit longer if people would communicate about such things. I'm fairly sure you didn't cause the thaw. :-) However, there's still the problem of binary packages ending up in the release snapshots without prominent notices of obsoleteness. The FreeBSD ports tree is not pegged to releases as in other systems. So if a -release user downloads a ports tree, he gets the same tree as someone who is using -current. You do have a point that obsolete versions will end up on the snapshots of the ports tree on cds. We have a perfectly good mechanism for dealing with this, it's called NO_CDROM. I would be happy to add this to the Makefile. I don't think RCs and development snapshots should end up there at all. I don't share your opinion about RCs. Regarding development snapshots, however, the port was named 'ion3-devel' until the first RC - indicating quite clearly that building it gave you software in development. The only reason I did the rename at RC-time was because I thought a release would happen 'real soon' after. It didn't. Note that I'm not complaining about your release schedule. I should have waited with the repocopy until after the release. My fault. That's the problem with distros' megafreezes: you can't sync the development of thousands of packages. And as for stable releases, even they should get bugfixes promptly. Maybe the 28 day limit can be relaxed in such cases a bit, but even half a year may be too long -- two years like with Debian is certainly too long. I don't think there has ever been a FreeBSD ports freeze which lasted as long as six months, let alone two years. Generally a month or so is the order of magnitude. It depends on the bug at hand: segfaults should be fixed very promptly, whereas minor glitches are not that big deal. During ports freezes, approval from portmgr can be saught to fix things like segfaults. - Philip -- Philip PaepsPlease don't Cc me, I am [EMAIL PROTECTED] subscribed to the list. BOFH Excuse #180: ether leak ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 license violation
On 2007-12-13 05:02:36 (-0600), Mark Linimon [EMAIL PROTECTED] wrote: On Thu, Dec 13, 2007 at 11:42:53AM +0100, Philip Paeps wrote: Anyway. How does portmgr feel about this? Aye or nay? I do not yet believe that it is possible to meet Tuomo's interpretation of his license without his prior review of every possible patch, and I'm not willing to obligate the FreeBSD project, in perpetuity, to be able to do so. Assuming you have your portmgr hat on, I'll take this as a very clear nay and I won't add the port again. It's fairly easy to maintain locally in $HOME/bin for those of us who still feel it's the only usable window manager. :-) Thanks for the clarification! - Philip -- Philip PaepsPlease don't Cc me, I am [EMAIL PROTECTED] subscribed to the list. BOFH Excuse #234: Someone is broadcasting pygmy packets and the router doesn't know how to deal with them. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 license violation
On 2007-12-13, Mark Linimon [EMAIL PROTECTED] wrote: I do not yet believe that it is possible to meet Tuomo's interpretation of his license without his prior review of every possible patch, If you don't trust your judgement on significant vs. insignificant changes, you can just have the user review them: - Significantly altered versions may be provided only if the user explicitly requests for those modifications to be applied, and is prominently notified that the software is no longer considered the standard version, and is not supported by the copyright holder. The version string displayed by the program must describe these modifications and the support void status. This specifically allows shit like the Xft patch that I will have nothing to do with (not until enabling clear crisp unblurred fonts is no more effort than 'echo crisp = yes ~/.fonts.conf'), provided that users get an unmodified version unless they known what they're doing. -- Tuomo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 license violation
On Thu, Dec 13, 2007 at 11:01:50AM +, Tuomo Valkonen wrote: On 2007-12-13, Jeremy Chadwick [EMAIL PROTECTED] wrote: Does this help you understand things a bit better? I know how the system works. I've even tried using FreeBSD on a couple of occasions -- and every time dependencies among the source packages have been broken, etc. Alright, I just wanted to make sure you knew how it worked, because what you'd stated didn't sound accurate. Also, what relevancy does dependency issues have to the issue we've been discussing? *sigh* -- | 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: serious error possibly related to bsd.*.mk
on 13/12/2007 12:28 Rene Ladan said the following:
2007/12/13, Andriy Gapon [EMAIL PROTECTED]:
Anybody else seeing this ? Seems to be pretty serious if it's not my
local issue.
$ portupgrade graphviz
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
This is after portsnap five minutes before this writing.
Yes, it's been there since the ports thaw. It seems to be related to
graphics/graphviz/Makefile, the bsd.*.mk files haven't been altered
since
2007-12-04 (bsd.ruby.mk) so they should be ok.
Rene
Hmm, portlint also produces quite a bag of messages in that port:
$ portlint -A
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
WARN: Makefile: [316]: use ${VARIABLE}, instead of $(VARIABLE).
FATAL: Makefile: [264]: USE_RUBY is set after including bsd.port.pre.mk.
WARN: Makefile: [188]: is USE_XORG a user-settable option? Consider
using WITH_XORG instead.
WARN: Makefile: possible use of absolute pathname /nonexistent.
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section
empty, to make CVS happy.
FATAL: Makefile: CATEGORIES left blank. set it to misc if nothing
seems apropriate.
FATAL: Makefile: either PORTVERSION or DISTVERSION must be specified
Syntax error: Unterminated quoted string
WARN: Makefile: COMMENT should begin with a capital, and end without a
period
FATAL: breaks INDEX (/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed
conditional (${_USE_GNOME_ALL:Mpango}==) /usr/ports/Mk/bsd.port.mk,
line 6147: if-less endif make: fatal errors encountered -- cannot continue).
4 fatal errors and 5 warnings found.
Not sure which of them are relevant and which are just consequences.
This is from make -dA:
. if ${_USE_GNOME_ALL:Mpango}==
IGNORE= cannot install: Unknown component pango
. endif
_USE_GNOME+=${pango_USE_GNOME_IMPL} pango
at line 634
Global:delete component
Applying :M to
Result is
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serious error possibly related to bsd.*.mk
Sorry for top-posting. Just discovered that if I remove saved options
file then things seems to be better.
Here's what I had in the file:
_OPTIONS_READ=graphviz-2.12_2
WITH_TK=true
WITH_XPM=true
WITH_ICONV=true
WITH_NLS=true
WITH_PANGOCAIRO=true
WITH_PERL=true
WITHOUT_PHP=true
WITH_PYTHON=true
WITH_RUBY=true
WITH_LUA=true
WITH_TCL=true
WITH_GUILE=true
Not sure what exactly and why confused the port. I wasn't even able to
run make config.
Here's diff between old and new options just in case:
--- /tmp/optionsMon May 21 11:12:22 2007
+++ /var/db/ports/graphviz/options Thu Dec 13 14:27:03 2007
@@ -1,12 +1,18 @@
# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
-# Options for graphviz-2.12_2
-_OPTIONS_READ=graphviz-2.12_2
+# Options for graphviz-2.16
+_OPTIONS_READ=graphviz-2.16
WITH_TK=true
WITH_XPM=true
WITH_ICONV=true
WITH_NLS=true
WITH_PANGOCAIRO=true
+WITH_GTK=true
+WITHOUT_GDK_PIXBUF=true
+WITH_GNOMEUI=true
+WITHOUT_DIGCOLA=true
+WITHOUT_IPSEPCOLA=true
+WITHOUT_MING=true
WITH_PERL=true
WITHOUT_PHP=true
WITH_PYTHON=true
on 13/12/2007 13:55 Andriy Gapon said the following:
on 13/12/2007 12:28 Rene Ladan said the following:
2007/12/13, Andriy Gapon [EMAIL PROTECTED]:
Anybody else seeing this ? Seems to be pretty serious if it's not my
local issue.
$ portupgrade graphviz
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
This is after portsnap five minutes before this writing.
Yes, it's been there since the ports thaw. It seems to be related to
graphics/graphviz/Makefile, the bsd.*.mk files haven't been altered
since
2007-12-04 (bsd.ruby.mk) so they should be ok.
Rene
Hmm, portlint also produces quite a bag of messages in that port:
$ portlint -A
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
WARN: Makefile: [316]: use ${VARIABLE}, instead of $(VARIABLE).
FATAL: Makefile: [264]: USE_RUBY is set after including bsd.port.pre.mk.
WARN: Makefile: [188]: is USE_XORG a user-settable option? Consider
using WITH_XORG instead.
WARN: Makefile: possible use of absolute pathname /nonexistent.
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section
empty, to make CVS happy.
FATAL: Makefile: CATEGORIES left blank. set it to misc if nothing
seems apropriate.
FATAL: Makefile: either PORTVERSION or DISTVERSION must be specified
Syntax error: Unterminated quoted string
WARN: Makefile: COMMENT should begin with a capital, and end without a
period
FATAL: breaks INDEX (/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed
conditional (${_USE_GNOME_ALL:Mpango}==) /usr/ports/Mk/bsd.port.mk,
line 6147: if-less endif make: fatal errors encountered -- cannot continue).
4 fatal errors and 5 warnings found.
Not sure which of them are relevant and which are just consequences.
This is from make -dA:
. if ${_USE_GNOME_ALL:Mpango}==
IGNORE= cannot install: Unknown component pango
. endif
_USE_GNOME+=${pango_USE_GNOME_IMPL} pango
at line 634
Global:delete component
Applying :M to
Result is
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)]
On Wed, Dec 12, 2007 at 10:31:10PM -0500, Mikhail Teterin wrote: Maybe, their pissed-off threshold is just greater, and they were able to get through his fireworks without losing the sight of /their users/, who continue to like the software, however frustrating the author's fits... It's not an us and them situation. FreeBSD ports are created and maintained by the people who use the ports. If someone wants to use the software, they are free to provide a port that will comply with the license. So far one person has stated that they tried and gave up. Maybe the next person will be more successful. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpWdwWiuZin0.pgp Description: PGP signature
Re: serious error possibly related to bsd.*.mk
2007/12/13, Andriy Gapon [EMAIL PROTECTED]:
[..]
Not sure what exactly and why confused the port. I wasn't even able to
run make config.
Here's diff between old and new options just in case:
--- /tmp/optionsMon May 21 11:12:22 2007
+++ /var/db/ports/graphviz/options Thu Dec 13 14:27:03 2007
@@ -1,12 +1,18 @@
# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
-# Options for graphviz-2.12_2
-_OPTIONS_READ=graphviz-2.12_2
+# Options for graphviz-2.16
+_OPTIONS_READ=graphviz-2.16
WITH_TK=true
WITH_XPM=true
WITH_ICONV=true
WITH_NLS=true
WITH_PANGOCAIRO=true
+WITH_GTK=true
+WITHOUT_GDK_PIXBUF=true
+WITH_GNOMEUI=true
+WITHOUT_DIGCOLA=true
+WITHOUT_IPSEPCOLA=true
+WITHOUT_MING=true
WITH_PERL=true
WITHOUT_PHP=true
WITH_PYTHON=true
Applying this diff make things work again on my box :)
Rene
on 13/12/2007 13:55 Andriy Gapon said the following:
on 13/12/2007 12:28 Rene Ladan said the following:
2007/12/13, Andriy Gapon [EMAIL PROTECTED]:
Anybody else seeing this ? Seems to be pretty serious if it's not my
local issue.
$ portupgrade graphviz
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
This is after portsnap five minutes before this writing.
Yes, it's been there since the ports thaw. It seems to be related to
graphics/graphviz/Makefile, the bsd.*.mk files haven't been altered
since
2007-12-04 (bsd.ruby.mk) so they should be ok.
Rene
Hmm, portlint also produces quite a bag of messages in that port:
$ portlint -A
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
WARN: Makefile: [316]: use ${VARIABLE}, instead of $(VARIABLE).
FATAL: Makefile: [264]: USE_RUBY is set after including bsd.port.pre.mk.
WARN: Makefile: [188]: is USE_XORG a user-settable option? Consider
using WITH_XORG instead.
WARN: Makefile: possible use of absolute pathname /nonexistent.
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section
empty, to make CVS happy.
FATAL: Makefile: CATEGORIES left blank. set it to misc if nothing
seems apropriate.
FATAL: Makefile: either PORTVERSION or DISTVERSION must be specified
Syntax error: Unterminated quoted string
WARN: Makefile: COMMENT should begin with a capital, and end without a
period
FATAL: breaks INDEX (/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed
conditional (${_USE_GNOME_ALL:Mpango}==) /usr/ports/Mk/bsd.port.mk,
line 6147: if-less endif make: fatal errors encountered -- cannot continue).
4 fatal errors and 5 warnings found.
Not sure which of them are relevant and which are just consequences.
This is from make -dA:
. if ${_USE_GNOME_ALL:Mpango}==
IGNORE= cannot install: Unknown component pango
. endif
_USE_GNOME+=${pango_USE_GNOME_IMPL} pango
at line 634
Global:delete component
Applying :M to
Result is
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
--
Andriy Gapon
--
GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)
It won't fit on the line.
-- me, 2001
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: results of ports re-engineering survey
On Dec 13, 2007, at 02:32 , David Southwell wrote: I suspect antagonistic responsesfrom some people are more about wounded pride (i.e - astonishment why should anyone propose to improve on the procedures, systems and engineering to which they contributed in the past!) You suspect wrong. Sorry. Indeed, I already said as much about the current system, and it's scalability. Sp please either make contributions that are intended to help the current process rather than boring everyone with negativity Since this is a WIP, how about taking it to a specific mailing list that is not related to how things currently operate. I read ports@ for one reason, and one reason only, to keep abreast of potential issues with the *current* system. It's not hard to set up a mailing list. Hell, I'll even host it myself if that's what it takes, but as things stand, ports@ (or, indeed, any other exising mailing list) is not the right place to be discussing concepts that are, fluid. -aDe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: results of ports re-engineering survey
Ade Lovett wrote: On Dec 13, 2007, at 02:32 , David Southwell wrote: I suspect antagonistic responsesfrom some people are more about wounded pride (i.e - astonishment why should anyone propose to improve on the procedures, systems and engineering to which they contributed in the past!) You suspect wrong. Sorry. Indeed, I already said as much about the current system, and it's scalability. Sp please either make contributions that are intended to help the current process rather than boring everyone with negativity Since this is a WIP, how about taking it to a specific mailing list that is not related to how things currently operate. I read ports@ for one reason, and one reason only, to keep abreast of potential issues with the *current* system. It's not hard to set up a mailing list. Hell, I'll even host it myself if that's what it takes, but as things stand, ports@ (or, indeed, any other exising mailing list) is not the right place to be discussing concepts that are, fluid. Why cannot ports@ be a broad commons? It is not as if David and Aryeh are posting oodles of spam! Definitely their postings are totally pertinent to Porting software to FreeBSD (http://lists.freebsd.org/mailman/listinfo). And what is all this talk of them polluting the list? Far more noise has been generated complaining about them. I understand that you might have a private definition of ports@ that it should only discuss the current system. But if this is all you come to this group for, just press the delete key when it is not something you are personally interested in. Now if someone starts talking about their vacation plans, or even FreeBSD kernel issues, then by all means complain about list pollution - I'll join with you! Stephen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)]
On четвер 13 грудень 2007, Peter Jeremy wrote: = So far one person has stated that they tried and gave = up. Maybe the next person will be more successful. Absolutely right. My point, however, was that the rashed removal makes that hypothetical next person's job more difficult. No, not impossible -- getting stuff out from the Attic is doable. But more difficult (possibly involving contacting repo-meisters, etc.) -- we have the EXPIRATION_DATE setting for a reason. Any claims of license violations -- which, according to Mark, lead to the hasty removal -- should've been addressed by using FORBIDDEN/IGNORE instead. Not much can be done /now/ -- the reason I'm making these noises is to prevent another disorderly deorbiting of a port in the future. -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
make index doesn't work
Hi,
I've been trying to find a solution to my problem via Google or
freebsd-ports' group archive but maybe you can help.
The problem is: I run cvsup, go into /usr/ports and type make index. After
some minutes I get the following error message:
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
=== graphics/graphviz failed
*** Error code 1
1 error
I run cvsup every day for over half a year. I encountered the above
problem a few days ago.
I'm using FreeBSD 6.2-Release. My /etc/make.conf:
CPUTYPE=athlon-xp
CFLAGS= -O2 -pipe
CXXFLAGS+= -fconserve-space
MAKE_SHELL=sh
COPTFLAGS= -O -pipe
INSTALL=install -C
DOC_LANG= en_US.ISO8859-1 pl_PL.ISO8859-2
WITH_NVIDIA_GL=yes
PERL_VER=5.8.8
PERL_VERSION=5.8.8
Thanks for help.
Bernard
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
In response to Tuomo Valkonen [EMAIL PROTECTED]: On 2007-12-13, Mark Linimon [EMAIL PROTECTED] wrote: On Thu, Dec 13, 2007 at 08:30:06AM +, Tuomo Valkonen wrote: The copyright holder reserves the right to refine the definition of significant changes on a per-case basis. In other words, a moving target -- which implies, to me, that to be legally in the clear, that we would first have to vet every possible change or modification, including patches. Notice the a priori: it means you're allowed to do that without legal threat until further notice to the contrary. Did you not understand the part where Mark described the requirement to avoid possible legal trouble? Since you felt the need to snip out the part of Mark's post that was truly relevant to your reply, I'll reproduce it here: But in the case of implied threat of legal action, in my opinion, it's not worth anyone's time to try to iterate over every possibility to find out to make sure they -- and others, on their behalf -- aren't somehow liable. The risk is simply too high. Stop abusing this mailing list for your own purposes. Let's state some facts: *) FreeBSD has agreed to remove the offending port in order to comply with your license requirements. However, you continue to complain. *) _Anyone_ could submit a patch to the port to abide by your license requirements and it's likely that it will be committed, yet _nobody_ has. Even you, Tuomo, claim to have bold and revolutionary ideas on package distribution yet would rather argue than WRITE A PATCH AND SUBMIT IT! Beyond that, you've _IGNORED_ posts that I've made in the past suggesting this. *) You blame distro folks as abusing developers and expecting them to just provide free work, then you turn around an complain that the FreeBSD people should bend over backwards to accommodate the software you wrote. You're doing the _exact_ thing you accuse others of doing. *) You continually abuse this mailing list by twisting other persons posts to your agenda by snipping relevant information, replying only to the parts that you want to, and redirecting the meaning of other posts. Please go somewhere that you can find emotional healing Tuomo. I, for one, will be glad to see you return as a sane person but have no desire to watch this thread continue as long as you're sick. -- 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: serious error possibly related to bsd.*.mk
On Thu, 13 Dec 2007 14:09:31 +0100 Rene Ladan [EMAIL PROTECTED] wrote: Applying this diff make things work again on my box :) I had a problem with this last night, but I just resynced, and all my ports upgraded correctly, so I guess it's fixed now. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
On 2007-12-13, Bill Moran [EMAIL PROTECTED] wrote: Did you not understand the part where Mark described the requirement to avoid possible legal trouble? Which part of my reply did you not understand? And at least where I come from, contracts are legally enforceable, even if they're only oral ones -- which would certainly include permissions given on a public mailing list. *) FreeBSD has agreed to remove the offending port in order to comply with your license requirements. However, you continue to complain. And you continue to spread misinformation, which I want to correct. *) _Anyone_ could submit a patch to the port to abide by your license requirements and it's likely that it will be committed, yet _nobody_ has. Wrong; see a recent post by the portmgr. Even you, Tuomo, claim to have bold and revolutionary ideas on package distribution yet would rather argue than WRITE A PATCH AND SUBMIT IT! Beyond that, you've _IGNORED_ posts that I've made in the past suggesting this. I have other things to do than learn yet another packaging system. Those things include fixing things in Ion3, so that a stable release could eventually be made. *) You blame distro folks as abusing developers and expecting them to just provide free work, then you turn around an complain that the FreeBSD people should bend over backwards to accommodate the software you wrote. You're doing the _exact_ thing you accuse others of doing. As others have stated, it's not difficult to comply with the license. But people are getting paranoid. *) You continually abuse this mailing list by twisting other persons posts to your agenda by snipping relevant information, replying only to the parts that you want to, and redirecting the meaning of other posts. Good to hear you're not alone. Please go somewhere that you can find emotional healing Tuomo. I, for one, will be glad to see you return as a sane person but have no desire to watch this thread continue as long as you're sick. Healthy mind in a healthy body. The social body of the FOSS movement is sick. -- Tuomo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD: Ion3 removal (Re: Ion3 license violation)]
On Thu, Dec 13, 2007 at 09:23:24AM -0500, Mikhail Teterin wrote: No, not impossible -- getting stuff out from the Attic is doable. But more difficult (possibly involving contacting repo-meisters, etc.) Wrong. You do cvs add, cvs com. Any claims of license violations -- which, according to Mark, lead to the hasty removal -- should've been addressed by using FORBIDDEN/IGNORE instead. At least in the US, a court of law won't accept we'll be deleting the infringing software Pretty Soon. Once notified of the infringement, you are obliged to take immediate action. Keeping us legal is an explicit part of the portmgr charter. If you think otherwise, please contact core@ and they can explain it to you. I doubt you'll take my word for it. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)]
In response to Mikhail Teterin [EMAIL PROTECTED]: On четвер 13 грудень 2007, Peter Jeremy wrote: = So far one person has stated that they tried and gave = up. Maybe the next person will be more successful. Absolutely right. My point, however, was that the rashed removal makes that hypothetical next person's job more difficult. There was nothing rash about it. Any lawyer will tell you that under the threat of legal action, you remove the threat, _then_ look in to creative ways to fix the problem. There was not an immediate answer to hand. As a result, Mark did the right thing and protected the FreeBSD project from any potential legal action until a better solution can be found. Any claims of license violations -- which, according to Mark, lead to the hasty removal -- should've been addressed by using FORBIDDEN/IGNORE instead. Perhaps you're right. However, I'd like to hear the opinion of a lawyer as to whether this is acceptable or not. -- 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]
problem to reach a maintainer
Dear I try to send a bug report to: [EMAIL PROTECTED] for tclhttpd-3.5.1_2 but ÉI got this error VotreFreeBSD Port: tclhttpd-3.5.1_2 document : n'a pas été [EMAIL PROTECTED] distribué à : Motif : Router: Failed to connect to SMTP host ALDAN.ALGEBRA.COM because : The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists. Thank you in advance for your help Yves___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal
On четвер 13 грудень 2007, Mark Linimon wrote: = Wrong. You do cvs add, cvs com. That would lose the prior history of the port, AFAIK. = At least in the US, a court of law won't accept we'll be deleting the = infringing software Pretty Soon. Once notified of the infringement, you = are obliged to take immediate action. FORBIDDEN prevents the port from being built just as immediately. You can then proceed to remove the already built packages from the ftp-site, which was done anyway. It is perfectly clear from the thread(s) -- and most participants don't even deny it -- that the personal feelings towards Tuomo have hastened the port's demise. Despite the ongoing port-freeze... I share some of the feeling, but we add/remove ports to improve the experience of users (including ourselves), not of the authors. = Keeping us legal is an explicit part of the portmgr charter. The surest thing to do so is to remove the entire ports collection -- it is all a major liability: http://technocrat.net/d/2006/6/30/5032 Tuomo's demands aren't unheard of either -- Sun's requirement, that Java binaries be certified isn't that different... And, unlike Tuomo, they already have brought a major lawsuit against a license-violator. But we continue to have JDK-ports (we just don't distribute the resulting binaries)... Bill Moran wrote: = should've been addressed by using FORBIDDEN/IGNORE instead. = Perhaps you're right. However, I'd like to hear the opinion of a lawyer = as to whether this is acceptable or not. The (mathematical) expectactions of the payments to lawyers equal the amount multiplied by the probability of having to pay. You are suggesting a payment of $200-$300 (for consultation) with the probability of 1 against the $10K-20K multiplied by, uhm, something so close to zero, that it may not fit in this message. If anybody ever does file a suit against FreeBSD, it will not be Tuomo. The thread has riched the sad point of tiring the readers regardless of contents long ago, and the port-maintainer has finally chimed in saying, he is going to resurrect the port portmgr-permitting. The portmgr implied permission already, so let's get back to coding. Tuomo Valkonen wrote: = However, there's still the problem of binary packages ending up in the = release snapshots without prominent notices of obsoleteness. So, like Java and others, let's mark this port (upon ressurection) RESTRICTED and NO_CDROM so that binaries aren't distributed and the user always has to build from source -- but with the port's aid. The Xinerama can be among the OPTIONS (default off) thus respecting the requirement, that modifications be only on user's request. -mi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
On Thu, Dec 13, 2007 at 02:43:07PM +, Tuomo Valkonen wrote: And at least where I come from, contracts are legally enforceable, even if they're only oral ones You clearly don't come from the US, where oral contracts are not germane in business law. What's written down in the license is the only thing that would be germane in court. Again, I'm not a lawyer, but this was my clear understanding from the courses I took. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make index doesn't work
2007/12/13, Bernard Nowakowski [EMAIL PROTECTED]:
Hi,
I've been trying to find a solution to my problem via Google or
freebsd-ports' group archive but maybe you can help.
The problem is: I run cvsup, go into /usr/ports and type make index. After
some minutes I get the following error message:
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
=== graphics/graphviz failed
*** Error code 1
1 error
I run cvsup every day for over half a year. I encountered the above
problem a few days ago.
[..setup..]
This should have been fixed by now. If you still have problems, read
the thread serious error possibly related to bsd.*.mk on this list.
HTH,
Rene
--
GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6
(subkeys.pgp.net)
It won't fit on the line.
-- me, 2001
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
miro Loading Miro Guide forever
Hi, I've been trying to use multimedia/miro but I am having a problem. I cannot access the Miro Guide. On startup, miro delivers the message Loading Miro Guide and it stays there indefinitely. I've left my laptop unattended for a couple of hours but nothing changed. miro seems to be working otherwise. I can search videos, create channels and watch/download videos. I am attaching the script(1) output. Let me know if there is anything I can do to help. Regards, -- Mario S F Ferreira - DF - Brazil - I guess this is a signature. feature, n: a documented bug | bug, n: an undocumented feature ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Renaming a Port
Greetings- I am the maintainer of the mysqltoolkit port. Recently, the project underwent a name change and is now maatkit. The application has also undergone some updates so I would like to update the port to the latest version. While I am sure I am not the first person to ever have this problem, its a new one for me so I figured I would ping the list and see what people have to say. Is this the best way to go about this? 1) Have someone mark mysqltoolkit as DEPRECATED 2) Take my port, rename it to maatkit and make the changes necessary to the Makefile, etc 3) Submit the port and have it checked in. However, do I need to provide some sort of migration path for existing users of mysqltoolkit? Is that even possible? If so, how do I go about doing it. Any advice or guidance is greatly appreciated. Thanks -- Steven Kreuzer http://www.exit2shell.com/~skreuzer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal
On 2007-12-13, Mikhail Teterin [EMAIL PROTECTED] wrote: The Xinerama can be among the OPTIONS (default off) thus respecting the requirement, that modifications be only on user's request. It's ok that it's an ion-specific option that is clearly documented to add an unsupported feature. However, as I have stated, it would be cleaner and maybe even more discoverable for the module to be a separate package. (There are other extra modules as well: mod_xrandr and mod_ionflux.) -- Tuomo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Limitations of Ports System
This thread was called results of ports re-engineering survey but I figured I would start a new thread. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. I would be interested in reading about some of the limitations people have run into when using ports. -- Steven Kreuzer http://www.exit2shell.com/~skreuzer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: results of ports re-engineering survey
Stephen Montgomery-Smith writes: I understand that you might have a private definition of ports@ that it should only discuss the current system. But if this is all you come to this group for, just press the delete key when it is not something you are personally interested in. I have no such restriction, I think complaints are on-topic. I wish those trying to build a better mousetrap prompt and complete success. And I congratulate them for putting code on paper. On the other hand ... once the discussion has moved from Something oughta be done. to We've started a project. - especially one that will generate enough light (never mind heat) on its own, it's time to take it elsewhere (within the larger FreeBSD environment). Wiki, special mailing list, private mailing list, whatever works. If I'm interested in the project, I gain by having all the bits in one place and not having to filter against the generic java/OpenOffice/fill in the blank won't compile/is slow/ate my poodle traffic. If I'm not interested in the project, well, we can all fill in the details. A monthly or bi-weekly announcement would not be out of line. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
In response to [EMAIL PROTECTED] (Mark Linimon): On Thu, Dec 13, 2007 at 02:43:07PM +, Tuomo Valkonen wrote: And at least where I come from, contracts are legally enforceable, even if they're only oral ones You clearly don't come from the US, where oral contracts are not germane in business law. What's written down in the license is the only thing that would be germane in court. Again, I'm not a lawyer, but this was my clear understanding from the courses I took. As a side note ... when I owned part of a business we had to got to court with a few clients over gross misunderstandings. As a result, I had a lawyer tell me exactly what you said: That verbal agreements _are_ legally binding, but almost never enforceable. As a result, they're not really germane to business law. At one point, a judge took me aside an told me to start making my clients sign agreements before doing any work, otherwise I was going to end up in serious trouble at some point. It's the reason why, in the US, agreeing to anything over the phone is a bad idea. Ever have a pushy salesman on the phone try to get you to agree to something _right_away_! They reason they do that is it's pretty much impossible to make them liable for misrepresentation or anything like that if you don't have it in writing. They can basically lie through their teeth and promise you the world without delivering, and it's damn near impossible to take legal action against them if it was all verbal. Of course, I am not a lawyer either, so you should consult with one before entering into any important agreement. -- 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: Renaming a Port
On Thu, Dec 13, 2007 at 10:31:01AM -0500, Steven Kreuzer wrote: Greetings- I am the maintainer of the mysqltoolkit port. Recently, the project underwent a name change and is now maatkit. The application has also undergone some updates so I would like to update the port to the latest version. While I am sure I am not the first person to ever have this problem, its a new one for me so I figured I would ping the list and see what people have to say. Is this the best way to go about this? 1) Have someone mark mysqltoolkit as DEPRECATED 2) Take my port, rename it to maatkit and make the changes necessary to the Makefile, etc 3) Submit the port and have it checked in. However, do I need to provide some sort of migration path for existing users of mysqltoolkit? Is that even possible? If so, how do I go about doing it. Any advice or guidance is greatly appreciated. The MOVED file exists for this very reason. You will need to submit an update that changes the current port to the new name and adds an entry to MOVED. A repocopy will be performed to copy the history of the port to the new location. Once that's done, the changes will be applied to the new copy, the entry added to MOVED, and the old port removed. -- Brooks pgpMLYcFltS3J.pgp Description: PGP signature
Re: rebuilding Postfix to ad MySQL support
jekillen wrote: Hello; Can I get some advice: I have Postfix installed from package at system install. I am trying to set up Cyrus Imap and Cyradm. These have specified use of mysql for database types. After carefully crafting the configuration files for Postfix, I am informed tha Postfix does not support MySQL tables as it stands. I have received instruction from Postfix list about how to add the support: $ make -f Makefile.init makefiles \ 'CCARGS=-DHAS_MYSQL -I/usr/local/include/mysql' \ 'AUXLIBS=-L/usr/local/lib/mysql -lmysqlclient -lz -lm' Wietsed I assume this is done in the Postfix port dir (and, impatiently, I am wondering if this is the correct syntax for csh). My question is: should I de-install the existing Postfix package first? I have laboriously crafted main.cf and the various database files. I could copy them somewhere else and re instate them. But why if the existing configuration files won't be bothered. Please forgive my novice* user level. I am learning as I go along. I am a hobbyist at this stage. Perhaps tomorrow, who knows? * I am a little beyond 'newby' but not by much. Thank you in advance Jeff K Jeff, You need select MYSQL option in make config in postfix port. cd /usr/ports/mail/postfix make config - Select MYSQL option in menu make all deinstall install clean DONE Now you can use postfix with mysql support. Regards ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Marcus Alves Grando marcus(at)sbh.eng.br | Personal mnag(at)FreeBSD.org | FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: serious error possibly related to bsd.*.mk
on 13/12/2007 15:56 Dirk Meyer said the following:
Hallo Andriy Gapon,
Here's diff between old and new options just in case:
--- /tmp/optionsMon May 21 11:12:22 2007
+++ /var/db/ports/graphviz/options Thu Dec 13 14:27:03 2007
@@ -1,12 +1,18 @@
# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
-# Options for graphviz-2.12_2
-_OPTIONS_READ=graphviz-2.12_2
+# Options for graphviz-2.16
+_OPTIONS_READ=graphviz-2.16
WITH_TK=true
WITH_XPM=true
WITH_ICONV=true
WITH_NLS=true
WITH_PANGOCAIRO=true
+WITH_GTK=true
+WITHOUT_GDK_PIXBUF=true
+WITH_GNOMEUI=true
+WITHOUT_DIGCOLA=true
+WITHOUT_IPSEPCOLA=true
+WITHOUT_MING=true
WITH_PERL=true
WITHOUT_PHP=true
WITH_PYTHON=true
That is very strange.
I habe no idea yet why this fails.
I noticed that if comment out WITH_GTK in the options file or turn off
GTK option via 'make config' (so that it becomes WITHOUT_GTK) then the
problem comes back. So there must be something 'magic' about it.
Hmm, if I comment out the following lines:
.if defined(WITH_GTK)
.include ${PORTSDIR}/Mk/bsd.gnome.mk
.endif
Then I also get the error:
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mgtk20}==)
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mlibgnomeui}==)
So it seems that in this case bsd.gnome.mk still gets sucked in but in
some improper way. This probably happens when 'IGNORE' should have
became active i.e. GTK is off but something depending on it is on.
Having though about it - maybe this is because USE_GNOME becomes defined
so bsd.gnome.mk get included via bsd.port.mk (via bsd.port.post.mk, in
turn).
I think there could be two solutions: either not set USE_GNOME unless
WITH_GTK is defined or add or case for USE_GNOME before inclusion of
bsd.gnome.mk. Or even include it unconditionally.
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem to reach a maintainer
--On Thursday, December 13, 2007 10:17:43 -0500 [EMAIL PROTECTED] wrote: Dear I try to send a bug report to: [EMAIL PROTECTED] for tclhttpd-3.5.1_2 but ÉI got this error VotreFreeBSD Port: tclhttpd-3.5.1_2 document : n'a pas été [EMAIL PROTECTED] distribué à : Motif : Router: Failed to connect to SMTP host ALDAN.ALGEBRA.COM because : The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists. Dig shows a resolvable host and dig -t MX shows a correctly configured MTA. Try again. It's likely exactly what the error message says - network problems or the server was down. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
--On Thursday, December 13, 2007 10:17:16 + Tuomo Valkonen [EMAIL PROTECTED] wrote: On 2007-12-13, Mark Linimon [EMAIL PROTECTED] wrote: On Thu, Dec 13, 2007 at 08:30:06AM +, Tuomo Valkonen wrote: The copyright holder reserves the right to refine the definition of significant changes on a per-case basis. In other words, a moving target -- which implies, to me, that to be legally in the clear, that we would first have to vet every possible change or modification, including patches. Notice the a priori: it means you're allowed to do that without legal threat until further notice to the contrary. ^^^ Geez, IANAL, nor do I have a dog in this fight, but if *you* can't see that the underlined phrase places the object of the clause in constant and persistent legal jeopardy, then perhaps *you* need to hire a lawyer. Let me see if I can boil this down to simple English. The license is what is is, unless and until I say it's not. Therefore, you can use it, for now, but you need to pay close attention because I might change it at some point in the future and *then* you will be liable. sarcasmYeah, I'm going to sign up for that one./sarcasm While watching this thread, I at first thought the decision to remove your software was a bit arbitrary. You have convinced me otherwise. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: miro Loading Miro Guide forever
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mario Sergio Fujikawa Ferreira wrote: Hi, I've been trying to use multimedia/miro but I am having a problem. I cannot access the Miro Guide. On startup, miro delivers the message Loading Miro Guide and it stays there indefinitely. I've left my laptop unattended for a couple of hours but nothing changed. miro seems to be working otherwise. I can search videos, create channels and watch/download videos. I am attaching the script(1) output. Let me know if there is anything I can do to help. Did you build against boost or boost-python? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYWg4zIOMjAek4JIRAuWSAJ91w9kVzOV+uRZ65YtidOdNnnu0rgCdGipw nyn5HOlM8biZfFSrZ6FAFV8= =U5ty -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
On 2007-12-13, Bill Moran [EMAIL PROTECTED] wrote: I had a lawyer tell me exactly what you said: That verbal agreements _are_ legally binding, but almost never enforceable. That may be because typical verbal agreements are difficult to prove. However, a statement on, say, a public mailing list is more provable. Of course, there's the question whether the message was really written by the person the message claims to be from. This situation could be improved by the person in question having a habit of signing messages (or, say, the software releases themselves) with PGP. Of course, that's not 100% reliable, but neither are ink-on-paper signatures. -- Tuomo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ion3 removal (Re: Ion3 license violation)
On 2007-12-13, Paul Schmehl [EMAIL PROTECTED] wrote: The license is what is is, unless and until I say it's not. Therefore, you can use it, for now, but you need to pay close attention because I might change it at some point in the future and *then* you will be liable. Well, I suppose that part is a bit messy, and it might be better to leave that part more vague: up to what is (court considers) significant based on the other explanations. (That a priori stuff is not in the terms themselves, but in the explanations section. The terms only refer to significant changes. IANAL, but I think such explanations are less binding than the actual terms: they act to help interpret the terms.) -- Tuomo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: miro Loading Miro Guide forever
Le Jeu 13 déc 07 à 11:34:25 +0100, Mario Sergio Fujikawa Ferreira [EMAIL PROTECTED] écrivait : Hi, Hello, I've been trying to use multimedia/miro but I am having a problem. I cannot access the Miro Guide. On startup, miro delivers the message Loading Miro Guide and it stays there indefinitely. I've left my laptop unattended for a couple of hours but nothing changed. miro seems to be working otherwise. I can search videos, create channels and watch/download videos. I am attaching the script(1) output. Let me know if there is anything I can do to help. Your script shows that you built it against xulrunner, which is not enabled, and I have not tested this combination; could you please build it again, defining either WITH_GECKO=firefox or WITH_GECKO=seamonkey? Best regards, -- Th. Thomas. pgpzG03biJTGD.pgp Description: PGP signature
what's the difference between devel/cvsps and devel/cvsps-devel?
Well, not much it seems... except that the cvsps-devel port has not
been updated since 2005.
It looks like the cvsps-devel port is redundant.
Should I file a PR?
Here's a diff between the two:
diff -urN cvsps/CVS/Entries cvsps-devel/CVS/Entries
--- cvsps/CVS/Entries Fri Oct 12 13:39:25 2007
+++ cvsps-devel/CVS/Entries Fri Oct 12 13:39:25 2007
@@ -1,4 +1,4 @@
-/Makefile/1.9/Tue Mar 27 22:11:53 2007//
-/distinfo/1.6/Sat Aug 12 03:57:38 2006//
+/Makefile/1.11/Sun Jul 31 04:28:50 2005//
+/distinfo/1.7/Thu Nov 24 15:39:10 2005//
/pkg-descr/1.1/Sat Feb 9 09:38:49 2002//
D/files
diff -urN cvsps/CVS/Repository cvsps-devel/CVS/Repository
--- cvsps/CVS/RepositoryFri Oct 12 13:39:25 2007
+++ cvsps-devel/CVS/Repository Fri Oct 12 13:39:25 2007
@@ -1 +1 @@
-ports/devel/cvsps
+ports/devel/cvsps-devel
diff -urN cvsps/Makefile cvsps-devel/Makefile
--- cvsps/Makefile Wed Mar 28 00:11:53 2007
+++ cvsps-devel/MakefileSun Jul 31 06:28:50 2005
@@ -3,35 +3,27 @@
# Date Created:Feb 9, 2002
# Whom:ijliao
#
-# $FreeBSD: ports/devel/cvsps/Makefile,v 1.9 2007/03/27 22:11:53 stas Exp $
+# $FreeBSD: ports/devel/cvsps-devel/Makefile,v 1.11 2005/07/31 04:28:50 nork
Exp $
#
PORTNAME= cvsps
-PORTVERSION= 2.1
-PORTREVISION= 0
+DISTVERSION= 2.1
CATEGORIES=devel
MASTER_SITES= http://www.cobite.com/cvsps/
+PKGNAMESUFFIX?=-devel
-MAINTAINER=[EMAIL PROTECTED]
-COMMENT= Create patchset information from CVS
+MAINTAINER=[EMAIL PROTECTED]
+COMMENT= CVS patchsets
+
+CONFLICTS= cvsps-1.*
USE_GMAKE= yes
-ALL_TARGET=cvsps
MAN1= cvsps.1
PLIST_FILES= bin/cvsps
-.if !defined(NOPORTDOCS)
-PORTDOCS= README
-.endif
-
do-install:
${INSTALL_PROGRAM} ${WRKSRC}/cvsps ${PREFIX}/bin
${INSTALL_MAN} ${WRKSRC}/cvsps.1 ${MANPREFIX}/man/man1
-
-.if !defined(NOPORTDOCS)
- ${MKDIR} ${DOCSDIR}
- ${INSTALL_DATA} ${WRKSRC}/README ${DOCSDIR}
-.endif
.include bsd.port.mk
diff -urN cvsps/files/CVS/Entries cvsps-devel/files/CVS/Entries
--- cvsps/files/CVS/Entries Fri Oct 12 13:39:25 2007
+++ cvsps-devel/files/CVS/Entries Fri Oct 12 13:39:25 2007
@@ -1,2 +1,2 @@
-/patch-cvsps.c/1.1/Sat Aug 12 03:57:38 2006//
+/patch-cvsps.c/1.1/Sun Jul 31 04:28:51 2005//
D
diff -urN cvsps/files/CVS/Repository cvsps-devel/files/CVS/Repository
--- cvsps/files/CVS/Repository Fri Oct 12 13:39:25 2007
+++ cvsps-devel/files/CVS/RepositoryFri Oct 12 13:39:25 2007
@@ -1 +1 @@
-ports/devel/cvsps/files
+ports/devel/cvsps-devel/files
diff -urN cvsps/files/patch-cvsps.c cvsps-devel/files/patch-cvsps.c
--- cvsps/files/patch-cvsps.c Sat Aug 12 05:57:38 2006
+++ cvsps-devel/files/patch-cvsps.c Sun Jul 31 06:28:51 2005
@@ -1,12 +1,13 @@
cvsps.c.orig Wed Aug 9 21:59:54 2006
-+++ cvsps.cWed Aug 9 22:00:17 2006
-@@ -2551,8 +2551,8 @@
+--- cvsps.c.orig Sun Jul 31 13:23:28 2005
cvsps.cSun Jul 31 13:23:36 2005
+@@ -2550,9 +2550,9 @@
+
for (next = ps-members.next; next != ps-members; next = next-next)
{
++ int d1, d2;
PatchSetMember * psm = list_entry(next, PatchSetMember, link);
-- rev = psm-pre_rev;
- int d1, d2;
-+ rev = psm-pre_rev;
+ rev = psm-pre_rev;
+- int d1, d2;
/* the reason this is at all complicated has to do with a
* branch off of a branch. it is possible (and indeed
--
stefan
http://stsp.name PGP Key: 0xF59D25F0
pgp9bvBKO0iv4.pgp
Description: PGP signature
Re: results of ports re-engineering survey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ade Lovett wrote: On Dec 13, 2007, at 02:32 , David Southwell wrote: I suspect antagonistic responsesfrom some people are more about wounded pride (i.e - astonishment why should anyone propose to improve on the procedures, systems and engineering to which they contributed in the past!) You suspect wrong. Sorry. Indeed, I already said as much about the current system, and it's scalability. Sp please either make contributions that are intended to help the current process rather than boring everyone with negativity Since this is a WIP, how about taking it to a specific mailing list that is not related to how things currently operate. I read ports@ for one reason, and one reason only, to keep abreast of potential issues with the *current* system. It's not hard to set up a mailing list. Hell, I'll even host it myself if that's what it takes, but as things stand, ports@ (or, indeed, any other exising mailing list) is not the right place to be discussing concepts that are, fluid. As soon we get to the point where user input is less important (design, implementation and testing) it will move to it's own virtual discussion space, but as long as user input is a critical component of the work it will stay on [EMAIL PROTECTED] as several people have said this is the most appropriate place in the existing structure to do this. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYX43zIOMjAek4JIRAteMAJ9Lg2Adh9HIHj6LCeamz7y1amNZ7QCghVO0 2t00d2ZmcL743jGj8/ybjvg= =4/wj -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: miro Loading Miro Guide forever
Aryeh M. Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mario Sergio Fujikawa Ferreira wrote: Hi, I've been trying to use multimedia/miro but I am having a problem. I cannot access the Miro Guide. On startup, miro delivers the message Loading Miro Guide and it stays there indefinitely. I've left my laptop unattended for a couple of hours but nothing changed. miro seems to be working otherwise. I can search videos, create channels and watch/download videos. I am attaching the script(1) output. Let me know if there is anything I can do to help. Did you build against boost or boost-python? Against devel/boost WITH_PYTHON: # cd /usr/ports/devel/boost # make WITH_PYTHON=1 all deinstall install clean ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: results of ports re-engineering survey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Huff wrote: Stephen Montgomery-Smith writes: I understand that you might have a private definition of ports@ that it should only discuss the current system. But if this is all you come to this group for, just press the delete key when it is not something you are personally interested in. I have no such restriction, I think complaints are on-topic. I wish those trying to build a better mousetrap prompt and complete success. And I congratulate them for putting code on paper. On the other hand ... once the discussion has moved from Something oughta be done. to We've started a project. - especially one that will generate enough light (never mind heat) on its own, it's time to take it elsewhere (within the larger FreeBSD environment). Wiki, special mailing list, private mailing list, whatever works. If I'm interested in the project, I gain by having all the bits in one place and not having to filter against the generic java/OpenOffice/fill in the blank won't compile/is slow/ate my poodle traffic. If I'm not interested in the project, well, we can all fill in the details. A monthly or bi-weekly announcement would not be out of line. 1. See my reply to Ade 2. We are not at We have started a project stage yet... that will not occur until there is a reasonable grasp on the scope and top level requirements 3. As soon as 2 is satisfied I will happily move to a private space -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYX8GzIOMjAek4JIRAjKhAJ9PSgUAfELej7M/1xIGcfX+FDD9wgCfQPvL pHLDmDKJkbH4w3i9pttggho= =rGMy -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
On Thu, 13 Dec 2007, Steven Kreuzer wrote: This thread was called results of ports re-engineering survey but I figured I would start a new thread. Rightly so. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. I would be interested in reading about some of the limitations people have run into when using ports. Notable with the new modular Xorg is the speed of changes (install/deinstall/clean) when there are a lot of ports installed. Before modular xorg, 400 ports installed was a lot. 700 now is not surprising. Some profiling looking for areas which could benefit from speed optimization would be useful. That may have already been done but not publicized. -Warren Block * Rapid City, South Dakota USA ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steven Kreuzer wrote: This thread was called results of ports re-engineering survey but I figured I would start a new thread. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. Many of them are not documented... I use it at home and have run into a number of issues (I don't want to restart the flame war that was the previous thread please do a search of the lists for them)... they will be better documented ASAP since enumerating them is part of the re-engineering process I will be conducting (perhaps the last public one) survey specifically focused on features people want and ones that must not be eliminated. Most of them boil down to the ports system was not designed to handle the load it has and incorrectly assumed the following: 1. All maintainers while be extremely careful in how the specify dependency requirements 2. That even though there would be metaports there would none of the current mega metaports 3. Too much trust is placed by the system on the correctness of individual ports -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYYYszIOMjAek4JIRAiA3AJ4s7rHqFRVOMifUj0heeZ/ZzsylJgCdGO93 M0411X/H/NKNto2vi3jY4R4= =+FTw -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: results of ports re-engineering survey
On Dec 13, 2007, at 10:47 AM, Aryeh M. Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ade Lovett wrote: On Dec 13, 2007, at 02:32 , David Southwell wrote: I suspect antagonistic responsesfrom some people are more about wounded pride (i.e - astonishment why should anyone propose to improve on the procedures, systems and engineering to which they contributed in the past!) You suspect wrong. Sorry. Indeed, I already said as much about the current system, and it's scalability. Sp please either make contributions that are intended to help the current process rather than boring everyone with negativity Since this is a WIP, how about taking it to a specific mailing list that is not related to how things currently operate. I read ports@ for one reason, and one reason only, to keep abreast of potential issues with the *current* system. It's not hard to set up a mailing list. Hell, I'll even host it myself if that's what it takes, but as things stand, ports@ (or, indeed, any other exising mailing list) is not the right place to be discussing concepts that are, fluid. As soon we get to the point where user input is less important (design, implementation and testing) it will move to it's own virtual discussion space, but as long as user input is a critical component of the work it will stay on [EMAIL PROTECTED] as several people have said this is the most appropriate place in the existing structure to do this. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYX43zIOMjAek4JIRAteMAJ9Lg2Adh9HIHj6LCeamz7y1amNZ7QCghVO0 2t00d2ZmcL743jGj8/ybjvg= =4/wj -END PGP SIGNATURE- I'm more than happy to take the comments in kind and implement them in my work with pkg_install. I honestly see no problem with commenting / brainstorming as long as it's productive. I'm done with finals and have no major obligations to deal with outside my '9 to 5' (more like 4:30 to 11:30) with BestBuy, so the true coding starts now.. Cheers, -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
On Dec 13, 2007, at 10:17 AM, Warren Block wrote: On Thu, 13 Dec 2007, Steven Kreuzer wrote: This thread was called results of ports re-engineering survey but I figured I would start a new thread. Rightly so. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. I would be interested in reading about some of the limitations people have run into when using ports. Notable with the new modular Xorg is the speed of changes (install/ deinstall/clean) when there are a lot of ports installed. Before modular xorg, 400 ports installed was a lot. 700 now is not surprising. Some profiling looking for areas which could benefit from speed optimization would be useful. That may have already been done but not publicized. -Warren Block * Rapid City, South Dakota USA My hunch is that part of the problem lies in the fact (unfortunately) that everything's done via Makefiles and that there's a lot of redundancy to some extent with the operations performed by pkg_install and friends (at least from reading and writing the /var/ db/pkg* and /usr/ports/INDEX* files are concerned), in particular when dealing with non-slave / -master instances, and how make is invoking pkg_install(1). I don't have hard evidence to support that point though, and until that point is reached my comment is merely speculation. -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Garrett Cooper wrote: On Dec 13, 2007, at 10:17 AM, Warren Block wrote: On Thu, 13 Dec 2007, Steven Kreuzer wrote: This thread was called results of ports re-engineering survey but I figured I would start a new thread. Rightly so. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. I would be interested in reading about some of the limitations people have run into when using ports. Notable with the new modular Xorg is the speed of changes (install/deinstall/clean) when there are a lot of ports installed. Before modular xorg, 400 ports installed was a lot. 700 now is not surprising. Some profiling looking for areas which could benefit from speed optimization would be useful. That may have already been done but not publicized. -Warren Block * Rapid City, South Dakota USA My hunch is that part of the problem lies in the fact (unfortunately) that everything's done via Makefiles and that there's a lot of redundancy to some extent with the operations performed by pkg_install and friends (at least from reading and writing the /var/db/pkg* and /usr/ports/INDEX* files are concerned), in particular when dealing with non-slave / -master instances, and how make is invoking pkg_install(1). I don't have hard evidence to support that point though, and until that point is reached my comment is merely speculation. That is why I plan to use xorg as the test case for the new system namely if it builds xorg in the most efficent way possible then it will be considered good enough for release -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYY92zIOMjAek4JIRAjBoAJ4hi8xhHmreBMKHu7FMnDI+HkYDMACfQfxS wVcLDfmxx33RniSkKLsysYo= =ZLLP -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
On Thu, Dec 13, 2007 at 11:17:34AM -0700, Warren Block wrote: On Thu, 13 Dec 2007, Steven Kreuzer wrote: This thread was called results of ports re-engineering survey but I figured I would start a new thread. Rightly so. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. I would be interested in reading about some of the limitations people have run into when using ports. Notable with the new modular Xorg is the speed of changes (install/deinstall/clean) when there are a lot of ports installed. Before modular xorg, 400 ports installed was a lot. 700 now is not surprising. Some profiling looking for areas which could benefit from speed optimization would be useful. That may have already been done but not publicized. There were some modifications added to the ports tree earlier this year (I think it was) that resulted in some quite significant speedups when installing/deinstalling ports. There were quite a bit of discussions about it at the time at this list (or possibly one of the other freebsd- lists.) -- Insert your favourite quote here. Erik Trulsson [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: Limitations of Ports System
On Thu, Dec 13, 2007 at 10:42:43AM -0500, Steven Kreuzer wrote: This thread was called results of ports re-engineering survey but I figured I would start a new thread. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. I would be interested in reading about some of the limitations people have run into when using ports. One shortcoming is the lack of locking making parallell builds a bit unsafe. If you try to build both port A and port B at the same time, and both A and B depends (directly or indirectly) on port C which is not installed, then you can esily end up having two processes both trying to build C at the same time. This usually confuses both builds very badly making them fail. I also don't think there is any locking on /var/db/pkg making possibly somewhat unsafe trying to register the installation of two ports/packages at the same time. I have never noticed any actual problems with this though. Some sort of locking, making parallel builds safe, should be possible to add to the ports system without doing any sweeping changes. (I did look briefly at the makefiles, but did not find any obvious place to put the locking. I probably just did not look hard enough.) -- Insert your favourite quote here. Erik Trulsson [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: Limitations of Ports System
Steven Kreuzer wrote: This thread was called results of ports re-engineering survey but I figured I would start a new thread. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. I would be interested in reading about some of the limitations people have run into when using ports. My personal frustration is the great length of time it takes to do make index and pkg_version (which calls make -V PKGNAME). The problem is that make has to read the entire makefile, including all the includes, before it can decide the value of any variable. I spent quite a while looking for speed improvements in this particular area, and couldn't find anything. I think that you have to dispense with make as the tool that coordinates the building of the ports, and rethink it from scratch. (I more or less came to the conclusion that it would be better to wait ten years until computers are ten times faster, and that in the mean time I could live with this particular problem.) Stephen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
multimedia/mplayer doesn't build (default options)
cc -O2 -pipe -march=pentium4 -O3 -ffast-math -fomit-frame-pointer -I./libavcodec -I./libavformat -Wdisabled-optimization -Wno-pointer-sign -Wdeclaration-after-statement -I. -I. -I./libavutil -O2 -pipe -march=pentium4 -O3 -ffast-math -fomit-frame-pointer -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DHAVE_CONFIG_H -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -I/usr/local/include/SDL -I/usr/local/include -D_REENTRANT -I/usr/local/include/freetype2 -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/freetype2 -I../libavcodec -I../libavformat -Wdisabled-optimization -Wno-pointer-sign -Wdeclaration-after-statement -I. -I.. -I../libavutil -O2 -pipe -march=pentium4 -O3 -ffast-math -fomit-frame-pointer -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -DHAVE_CONFIG_H -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -I/usr/local/include/SDL -I/usr/local/include -D_REENTRANT -I/usr/local/include/freetype2 -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/freetype2 -c -o ad_libvorbis.o ad_libvorbis.c ad_libvorbis.c: In function 'decode_audio': ad_libvorbis.c:232: warning: passing argument 2 of 'ds_get_packet_pts' from incompatible pointer type ad_libvorbis.c:238: error: too few arguments to function 'vorbis_synthesis' gmake[1]: *** [ad_libvorbis.o] Error 1 gmake[1]: Leaving directory `/usr/obj/homeKamikaze.norad/usr/ports/multimedia/mplayer/work/MPlayer-1.0rc2/libmpcodecs' gmake: *** [libmpcodecs/libmpcodecs.a] Error 2 *** Error code 2 Stop in /usr/ports/multimedia/mplayer. *** Error code 1 Stop in /usr/ports/multimedia/mplayer. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
On Thu, Dec 13, 2007 at 03:00:54PM -0500, Aryeh M. Friedman wrote: That is why I plan to use xorg as the test case for the new system namely if it builds xorg in the most efficent way possible then it will be considered good enough for release You need to pick a much more complicated set of dependencies than Xorg. You should analyse the dependency tree across all ports and then take into account what happens when source changes occur unsynchronised. Take things like those that depend on the various Qt ports. You will see that some depend on Qt3 and others on Qt4. Then consider things that depend on the documentation ports. Please do not fall into the trap of simplifying the requirements and then finding a simpler solution. -- John Birrell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
I just wonder if you asked the general population, whether they'd rather have ports or packages, I bet most would vote for packages, aside from those that actually like watching the compilation output fly by. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Birrell wrote: On Thu, Dec 13, 2007 at 03:00:54PM -0500, Aryeh M. Friedman wrote: That is why I plan to use xorg as the test case for the new system namely if it builds xorg in the most efficent way possible then it will be considered good enough for release You need to pick a much more complicated set of dependencies than Xorg. You should analyse the dependency tree across all ports and then take into account what happens when source changes occur unsynchronised. Take things like those that depend on the various Qt ports. You will see that some depend on Qt3 and others on Qt4. Then consider things that depend on the documentation ports. Please do not fall into the trap of simplifying the requirements and then finding a simpler solution. I was not planning to skimp on the requirements at all but the test case is xorg... i.e. I will do my best to not compermise on features/requirements but xorg meets several criteria for being a good test (out of order building, alt. depends, large but seperatable DAG) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYbPXzIOMjAek4JIRAtmcAJ4rifRtYkufmyFU9LCxqMhx73kZ6ACfe7Nt Ojc2my7xjUH6xoyn+ysHM1U= =mB1y -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
On Thu, Dec 13, 2007 at 05:36:07PM -0500, Aryeh M. Friedman wrote: I was not planning to skimp on the requirements at all but the test case is xorg... i.e. I will do my best to not compermise on features/requirements but xorg meets several criteria for being a good test (out of order building, alt. depends, large but seperatable DAG) But it all comes from one source and is released as one set. You need to think about things that are released from different places with different dependencies at different times. And then allow for the lag of getting the FreeBSD part updated. -- John Birrell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Birrell wrote: On Thu, Dec 13, 2007 at 05:36:07PM -0500, Aryeh M. Friedman wrote: I was not planning to skimp on the requirements at all but the test case is xorg... i.e. I will do my best to not compermise on features/requirements but xorg meets several criteria for being a good test (out of order building, alt. depends, large but seperatable DAG) But it all comes from one source and is released as one set. You need to think about things that are released from different places with different dependencies at different times. And then allow for the lag of getting the FreeBSD part updated. Perl, python and other pre-reqs to xorg are not from the same source thus fit the requirement I should of been more specific by saying xorg+all pre-req ports. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYbZszIOMjAek4JIRAueZAJ9zDRfMpYYNrXrik1VYFLvEXW86/QCfVqNo smhJVbQZqx269CJnoK2NMAQ= =Hf6H -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: miro Loading Miro Guide forever
Thierry Thomas wrote:
Le Jeu 13 déc 07 à 11:34:25 +0100, Mario Sergio Fujikawa Ferreira [EMAIL
PROTECTED]
écrivait :
Hi,
Hello,
I've been trying to use multimedia/miro but I am having a problem. I
cannot access the Miro Guide. On startup, miro delivers the message
Loading Miro Guide and it stays there indefinitely. I've left my
laptop unattended for a couple of hours but nothing changed.
miro seems to be working otherwise. I can search videos, create
channels and watch/download videos.
I am attaching the script(1) output. Let me know if there is anything
I can do to help.
Your script shows that you built it against xulrunner, which is not
enabled, and I have not tested this combination; could you please build
it again, defining either WITH_GECKO=firefox or WITH_GECKO=seamonkey?
Okay. Checking ${WRKSRC}/platform/gtk-x11/setup.py shows that
xulrunner is always preferred over any other found GECKO options.
Actually, the WITH_GECKO is only controlling the port dependency and it
has no influence whatsoever on what setup.py will pick.
That said. I removed xulrunner from the list of possible setup.py
choices. Reinstalled and miro works with firefox. :)
I have a patch attached that rectifies this situation.
Regards,
--
Mario S F Ferreira - DF - Brazil - I guess this is a signature.
feature, n: a documented bug | bug, n: an undocumented feature
Index: files/patch-platform_gtk-x11_setup.py
===
RCS file:
/home/pcvs/ports/multimedia/miro/files/patch-platform_gtk-x11_setup.py,v
retrieving revision 1.1
diff -d -u -u -r1.1 patch-platform_gtk-x11_setup.py
--- files/patch-platform_gtk-x11_setup.py 11 Dec 2007 22:27:19 -
1.1
+++ files/patch-platform_gtk-x11_setup.py 13 Dec 2007 19:14:16 -
@@ -1,5 +1,5 @@
platform/gtk-x11/setup.py.orig 2007-10-31 17:05:49.0 +0100
-+++ platform/gtk-x11/setup.py 2007-11-01 12:44:27.0 +0100
+--- platform/gtk-x11/setup.py.orig 2007-11-12 23:22:34.0 -0200
platform/gtk-x11/setup.py 2007-12-13 17:00:44.0 -0200
@@ -46,6 +46,7 @@
###
@@ -26,26 +26,29 @@
)
MozillaBrowser Extension
-@@ -219,12 +224,15 @@
- if re.search(^xulrunner-xpcom, packages, re.MULTILINE):
- xpcom = 'xulrunner-xpcom'
- gtkmozembed = 'xulrunner-gtkmozembed'
--elif re.search(^mozilla-xpcom, packages, re.MULTILINE):
--xpcom = 'mozilla-xpcom'
--gtkmozembed = 'mozilla-gtkmozembed'
- elif re.search(^firefox-xpcom, packages, re.MULTILINE):
- xpcom = 'firefox-xpcom'
- gtkmozembed = 'firefox-gtkmozembed'
+@@ -216,15 +221,15 @@
+ packages = getCommandOutput(pkg-config --list-all)
+ except RuntimeError, error:
+ sys.exit(Package config error:\n%s % (error,))
+-if re.search(^xulrunner-xpcom, packages, re.MULTILINE):
+-xpcom = 'xulrunner-xpcom'
+-gtkmozembed = 'xulrunner-gtkmozembed'
++if re.search(^firefox-xpcom, packages, re.MULTILINE):
++xpcom = 'firefox-xpcom'
++gtkmozembed = 'firefox-gtkmozembed'
+elif re.search(^seamonkey-xpcom, packages, re.MULTILINE):
+xpcom = 'seamonkey-xpcom'
+gtkmozembed = 'seamonkey-gtkmozembed'
-+elif re.search(^mozilla-xpcom, packages, re.MULTILINE):
-+xpcom = 'mozilla-xpcom'
-+gtkmozembed = 'mozilla-gtkmozembed'
+ elif re.search(^mozilla-xpcom, packages, re.MULTILINE):
+ xpcom = 'mozilla-xpcom'
+ gtkmozembed = 'mozilla-gtkmozembed'
+-elif re.search(^firefox-xpcom, packages, re.MULTILINE):
+-xpcom = 'firefox-xpcom'
+-gtkmozembed = 'firefox-gtkmozembed'
else:
sys.exit(Can't find xulrunner-xpcom, mozilla-xpcom or firefox-xpcom)
-@@ -334,7 +342,7 @@
+@@ -334,7 +339,7 @@
data_files.append((dest_dir, listfiles(source_dir)))
# add the desktop file, icons, mime data, and man page.
@@ -54,7 +57,7 @@
if rv != 0:
raise RuntimeError(xine_extractor compilation failed. Possibly missing
libxine, gdk-pixbuf-2.0, or glib-2.0.)
-@@ -342,11 +350,11 @@
+@@ -342,11 +347,11 @@
data_files += [
('/usr/share/pixmaps',
glob(os.path.join(platform_dir, 'miro-*.png'))),
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make index doesn't work
On 12/13/07, Bernard Nowakowski [EMAIL PROTECTED] wrote:
Hi,
I've been trying to find a solution to my problem via Google or
freebsd-ports' group archive but maybe you can help.
The problem is: I run cvsup, go into /usr/ports and type make index. After
some minutes I get the following error message:
/usr/ports/Mk/bsd.gnome.mk, line 643: Malformed conditional
(${_USE_GNOME_ALL:Mpango}==)
/usr/ports/Mk/bsd.port.mk, line 6147: if-less endif
make: fatal errors encountered -- cannot continue
=== graphics/graphviz failed
*** Error code 1
1 error
I also had this problem when using pkg_version, what i did was to:
cd /usr/ports/graphics/graphviz
make rmconfig
Then when I ran pkg_version a second time it did't give this error.
Scot
___
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: ossp-uuid-1.6.0
Excellent. Thank you! Bradford Castalia Senior Systems Analyst Planetary Image Research Laboratory University of Arizona Build an image in your mind, fit yourself into it. Vasil Dimov wrote: On Thu, Dec 06, 2007 at 16:21:10 -0700, Bradford Castalia wrote: The current distribution package does not include the C++ API support. This is important for those of us depending on this API for support of applications that we are building and distributing. When building this package please include the --with-cxx configure option so the resulting package will be complete. Done. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
TeTeX and TeXLive
Hi all I'm just want known if there are any plan to replace teTeX ports (the project as stop) by TeXLive ? I've send long time ago a mail to teTeX maintainer and I don't have any answer. I known that's nothing urgent, but without tex the live is hard ;-) Regards. -- Albert SHIH Observatoire de Paris Meudon SIO batiment 15 Heure local/Local time: Ven 14 déc 2007 02:22:06 CET ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TeTeX and TeXLive
On Fri, 14 Dec 2007 02:24:09 +0100 Albert Shih [EMAIL PROTECTED] wrote: I'm just want known if there are any plan to replace teTeX ports (the project as stop) by TeXLive ? I've send long time ago a mail to teTeX maintainer and I don't have any answer. Me too. I must add that I tried two times to contact two FreeBSD developers who (according to the public sources) seemed to be interested in this; never got a single word of reply. Having in mind that I offered a help, some experience and maintaining/testing availability, I can't understand this. It's very discouraging. -- Nikola Lečić :: Никола Лечић ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Limitations of Ports System
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Danny Pansters wrote: On Thursday 13 December 2007 19:17:34 Warren Block wrote: On Thu, 13 Dec 2007, Steven Kreuzer wrote: This thread was called results of ports re-engineering survey but I figured I would start a new thread. Rightly so. On Dec 12, 2007, at 6:45 AM, Ade Lovett wrote: We *know* it can be done better. We *know* the scaling limits of the current system, and most of us are completely amazed it even still works. If y'all want to make a difference, concepts and ideas we have plenty of. Code talks. Out of curiosity, are any of these shortcomings documented anywhere? I have been using ports on my home machine for a long time and I've never had any problems with it. I assume the issues come into play when you work with multiple systems you are trying to keep in sync, etc. I would be interested in reading about some of the limitations people have run into when using ports. Notable with the new modular Xorg is the speed of changes (install/deinstall/clean) when there are a lot of ports installed. Before modular xorg, 400 ports installed was a lot. 700 now is not surprising. Some profiling looking for areas which could benefit from speed optimization would be useful. That may have already been done but not publicized. Well, I can tell you what I think: If we don't want thousands of global knobs, then it's either splitting up in almost atomic micro ports which inflates the number of ports or using port OPTIONS... BUT... we currently have no standard mechanism to actually use another port's OPTIONS in a somewhat generic way. It's all about where and how you want to have your granularity (sp?) I think. An other option is keep the knobs in a centeral DB but only ask for ones the port being currently being compiled requires and all other values are cached. Namely if I build abc with options 123 and 345 and def with 345 and 678 then 345 will be cached for def since we already set it for abc. In the longer run, being able to specify a port's options when specifying DEPENDS would probably be a very useful and not very invasive change for the better (or maybe if that's simpler -- doubt it -- some sort of OPT_DEPENDS). If someone wants to work specifically on addressing - to put it bluntly - the debianizing-ports-versus-optionifying-properly issue I'm interested in chipping in or if needed leading such an effort. The scope should be only that and it must be backwards compatible. There is enough dependancy (and alt versioning) issues they must be addressed also. The alt versioning alone will require a complete redesign I think thus we mightest well throw in port/package interchangability. So I am leaning towards a ground up rewrite unless some can show how to get real dependancy management and alt. versions into the existing framework. Note neither should complicate the current system any more then absulutely needed and any such compilcation should be on the maintainers and portmgr only (hopefully none). -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYfnizIOMjAek4JIRAisNAKCQ2VZ2wibSFinuKAztxJlvI6dbPQCdEgbQ SnHPQr+mrf9aImgj8iL7ZMI= =RuoC -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: cfengine-2.2.1
Sergie, I really appreciate your efforts with cfengine. I've discovered its use in maintaining 8 different sites with fairly complex configuration requirements. Is there any chance that you could update the kit to 2.2.3, as there won't be another upgrade to cfengine until June 2008, and the changes in 2.2.2 are desired :) . I've tried but its too complex - as a workaround I removed the files/patch* and kludged distinfo but it become stuck with docs during the make. Kind regards, Dewayne. ___ 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: cfengine-2.2.1
Dewayne Geraghty wrote: Sergie, I really appreciate your efforts with cfengine. I've discovered its use in maintaining 8 different sites with fairly complex configuration requirements. Is there any chance that you could update the kit to 2.2.3, as there won't be another upgrade to cfengine until June 2008, and the changes in 2.2.2 are desired :) . I've tried but its too complex - as a workaround I removed the files/patch* and kludged distinfo but it become stuck with docs during the make. Try http://www.freebsd.org/cgi/query-pr.cgi?pr=118562 -- Xin LI [EMAIL PROTECTED] http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: TeTeX and TeXLive
On Fri, 14 Dec 2007, Nikola Lečić wrote: On Fri, 14 Dec 2007 02:24:09 +0100 Albert Shih [EMAIL PROTECTED] wrote: I'm just want known if there are any plan to replace teTeX ports (the project as stop) by TeXLive ? I've send long time ago a mail to teTeX maintainer and I don't have any answer. Me too. I must add that I tried two times to contact two FreeBSD developers who (according to the public sources) seemed to be interested in this; never got a single word of reply. Having in mind that I offered a help, some experience and maintaining/testing availability, I can't understand this. It's very discouraging. please feel free to take that as a sign that you should take the ball and run with it. :) Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TeTeX and TeXLive
Hi, On 14/12/2007, Nikola Lečić [EMAIL PROTECTED] wrote: On Fri, 14 Dec 2007 02:24:09 +0100 Albert Shih [EMAIL PROTECTED] wrote: I'm just want known if there are any plan to replace teTeX ports (the project as stop) by TeXLive ? I've send long time ago a mail to teTeX maintainer and I don't have any answer. Me too. I must add that I tried two times to contact two FreeBSD developers who (according to the public sources) seemed to be interested in this; never got a single word of reply. Having in mind that I offered a help, some experience and maintaining/testing availability, I can't understand this. It's very discouraging. Some time ago I asked which TeX-Port would be the best, LaTeX oder teTeX. People here on this list recommended teTeX. TeXLive came up, too, and AFAIK there is work being done to include it in the ports system. But TeXLive is a distribution that contains loads of stuff that isn't needed with FreeBSD, and some parts don't fir into a FreeBSD system. So there's lots of work to be done and TeXLive can't be expected anytime soon. For more detail please see the list archives, I'm pretty sure I asked on questions@ but I can't access my own archives right now. HTH HAND Christian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
