On 08/02/2011 12:12, Andriy Gapon wrote:
> on 02/08/2011 21:26 Doug Barton said the following:
>> On 08/02/2011 06:14, Andriy Gapon wrote:
>>> Second, I think that portmaster could cache the origin => pkg mapping that
>>> it
>>> builds while working on po
I notice that http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/156253
exists for the 1.46.1 update, however 1.47 is out since July 11. I'm
curious about whatever plans may exist to do the update ...
Doug
--
Nothin' ever doesn't change, but nothin' changes much.
On 08/02/2011 13:39, Andriy Gapon wrote:
> Just a few small corrections:
I was using your description of the situation. Sorry if I misunderstood.
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of k
On 08/02/2011 15:34, JoelFRodriguez wrote:
> Are you serious? Upgrading the OS on a production machine is a really steep
> price to pay. I've over a thousand working ports and numerous customers that
> I would have to port afterwards.
FreeBSD 6 has been EOL since November 30, 2010. We have been en
On 08/02/2011 17:59, JoelFRodriguez wrote:
> This stuff has worked fine on my FREEBSD6.2 system until this week. And if I
> read these msgs correctly, this problem also occurs on FREEBSD8.
The current icu and glib20 ports work fine on all supported versions of
FreeBSD.
I think bapt's response was
On 08/03/2011 03:39, Andriy Gapon wrote:
> on 03/08/2011 00:09 Peter Jeremy said the following:
>> An alternative viewpoint is that this is wasteful because data is then
>> double-buffered.
>
> If you stop accessing data on disk after putting it into an application cache,
> then there would not be
On 07/31/2011 14:08, Doug Barton wrote:
> On 07/31/2011 07:08, Olivier Duchateau wrote:
>> Hi
>>
>> 2011/7/31, Doug Barton :
>>> Howdy,
>>>
>>> I decided to do my perennial "try other window managers" thing and the
>>> new versi
On 08/03/2011 20:20, Warren Block wrote:
> On Wed, 3 Aug 2011, Doug Barton wrote:
>
>> However this has lead to a new issue, the restart and shutdown icons are
>> greyed out when I click the "log out" menu item. I noticed that there is
>> a mention of this issu
This is on 7.x i386. Builds fine, and passes all self-tests.
Thanks,
Doug
( cd PerlMagick && gmake CC='cc -std=gnu99 -std=gnu99' && \
gmake CC='cc -std=gnu99 -std=gnu99' install )
gmake[3]: Entering directory
`/usr/local/tmp/usr/ports/graphics/ImageMagick-nox11/work/ImageMagick-6.7.0-10/PerlMa
On 08/23/2011 08:22, Heino Tiedemann wrote:
> Hi There
>
>
> ist is like a bite in your own ass (dead lock):
>
>
> [UODATING]: The default ruby version has been updated to 1.9. Please rebuild
> all ports that
>
>
>
> [AMAROK] BROKEN= does not build with ruby 1.9
>
>
>
>
> What To do
On Tue, 23 Aug 2011 22:35:30 +0200
Michel Talon wrote:
> It appears ruby-rbtree is marked deprecated because the master site
> has disappeared.
> In fact it has moved here:
> http://rubyforge.org/frs/download.php/67118/rbtree-0.3.0.tar.gz
Probably best to send a PR, that will ping the maintainer
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I just did the mondo upgrade of the ports on my up to date 8-current
laptop. Whereas before the upgrade the default video output would always
be the monitor attached to the dock if my laptop was in the dock (which
was what I wanted), now X re
Thanks for responding, sorry it took so long to get back to you,
$REAL_LIFE is in my face lately.
I was able to remove kde from the equation by starting good old
windowmaker, same results.
On Wed, 7 Nov 2007, Anton Berezin wrote:
On Tue, Nov 06, 2007 at 01:19:18PM -0800, Doug Barton wrote
This is very interesting stuff, but I don't see how it would be useful to
a very wide audience. My feeling is that the vast majority of our users
build and/or install ports as root, and I don't see any good reason for
that not to be the default practice.
I'll review your patch more thoroughly
On Tue, 6 Nov 2007, Doug Barton wrote:
I just did the mondo upgrade of the ports on my up to date 8-current
laptop. Whereas before the upgrade the default video output would always
be the monitor attached to the dock if my laptop was in the dock (which
was what I wanted), now X refuses to see
Scot Hetzel wrote:
>> On Sun, Nov 18, 2007 at 08:17:36PM -0500, Chuck Robey wrote:
>>> activate the port, and if so, the port would add a line of the form
>>> 'portname_enable="YES"', and this would make your new port operate.
>>> Well, it seems from what I see of my new system, that this is no lon
RW wrote:
> On Wed, 21 Nov 2007 12:14:17 -0800
> Doug Barton <[EMAIL PROTECTED]> wrote:
>
>> ... I have for some time wanted to add support
>> to rc.subr for a /usr/local/etc/rc.conf.d so that ports could install
>> sensible defaults for rc
Gergely CZUCZY wrote:
> echo 'sevice_enable="YES"' >> /etc/rc.conf.local
Yes, I think we all know how to go about this manually. The question
at hand is whether or not it's possible or desirable to create the
possibility of doing it for the user at port install time.
If what you're trying to say
On Mon, 19 Nov 2007, Jason C. Wells wrote:
What I am trying to do is to build 30 or so packages including the big ones
like X, kde, gnome, plus all of their dependencies on a build host and then
use pkg_add on various machines. I have had a variety of difficulties with
all of the methods I ha
On Thu, 22 Nov 2007, Gergely CZUCZY wrote:
Gergely CZUCZY wrote:
echo 'sevice_enable="YES"' >> /etc/rc.conf.local
I said, that this can be done from the Makefile as well, if that OPTIONS
of yours is enabled.
But that would violate the principle that ports shouldn't touch files in
/etc.
Jason C. Wells wrote:
> Doug Barton wrote:
>> On Mon, 19 Nov 2007, Jason C. Wells wrote:
>>
>>> What I am trying to do is to build 30 or so packages including the
>>> big ones like X, kde, gnome, plus all of their dependencies on a
>>> build host and the
Jason C. Wells wrote:
> Most of the message below is just rounding out the discussion. There is
> one significant question on recursion though.
Sounds good, I'll snip the bits that don't require comment.
> Doug Barton wrote:
>
>>> I also ended up with shared a li
In thinking about the guy who posted to -stable about using the tar'ed
up version of the ports tree, I had an idea that would make that more
useful. How hard would it be to include the c[v]sup checkouts file
with the tarball, and install it into some standard location? I think
that would greatly in
RW wrote:
> On Fri, 23 Nov 2007 20:00:59 -0800
> Doug Barton <[EMAIL PROTECTED]> wrote:
>> How hard would it be to include the c[v]sup checkouts file
>> with the tarball, and install it into some standard location? I think
>> that would greatly increase the uti
Kelly Hays wrote:
> Doug,
> Did you ever get this working? I have a simular problem and the
> workaround I found is to use the "nvidia-driver-96xx" port instead of
> the regular "nvidia-driver" port. I can not remember the exact model
> of the Dell FP display that I have ( it is at work) but it is
Edwin Groothuis wrote:
> On Sat, Nov 24, 2007 at 09:39:19AM +0100, Alex Dupre wrote:
>> Doug Barton wrote:
>>> In thinking about the guy who posted to -stable about using the tar'ed
>>> up version of the ports tree, I had an idea that would make that more
>
Edwin Groothuis wrote:
> On Sun, Nov 25, 2007 at 06:26:09PM -0800, Doug Barton wrote:
>> Edwin Groothuis wrote:
>>> On Sat, Nov 24, 2007 at 09:39:19AM +0100, Alex Dupre wrote:
>>>> Doug Barton wrote:
>>>>> In thinking about the guy who posted to -stab
GP wrote:
>>> Hi and welcome!
>>> First of all you should install ports-mgmt/portlint and run it against
>>> your port (if you haven't done it already). Be sure to use the switch to
>>> enable additional checks (I got bitten once because I forgot it).
>>> Then you could perhaps put your work onlin
On Mon, 3 Dec 2007, Heino Tiedemann wrote:
,
|/libexec/ld-elf.so.1:/usr/local/lib/perl5/5.8.8/mach/CORE/libperl.so:
| Undefined symbol
| "__sbmaskrune"
| *** Error code 1
|
| Stop in /usr/ports/graphics/ImageMagick.
`
What can I do?
Rebuild perl.
Doug
--
This .signature sanitiz
Clint Olsen wrote:
> I've tried redirecting standard output/error, both /bin/sh and /bin/csh,
> and I can't run this in batch. I'm trying to build gnome which takes
> hours, and I want it backgrounded so that if this SSH shell disconnects it
> doesn't crater the build. You would think that --batc
On Mon, 3 Dec 2007, Wes Morgan wrote:
On Tue, 4 Dec 2007, Stefan Sperling wrote:
Screen also has log functionality.
Toggle with: Ctrl+A, then Shift+H
You can also use "script" to capture the output fairly easily.
So you have to use two different programs, one of which is a port, to
accomp
Ben Kelly wrote:
> Maybe I am doing something wrong, but I have never been able to get
> nohup to work correctly with portupgrade for this sort of this. For
> example:
>
> ianto# nohup portupgrade -a >& /tmp/port.log &
You just want to do 'nohup portupgrade -a &'
output will be captured in nohu
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
If you're interested in xscreensaver support for pam and/or kerberos,
please take a look at
http://dougbarton.us/Downloads/xs-504-pam-kerberos.diff. You should
apply the patch with the --remove-empty-files option.
If I don't hear of any problems
Lockdown wrote:
> Hello, I was just wondering if you were working on the port for
> pidgin-2.3.0.
2.3.1 is already out, and the upgrade is pretty simple. Apply the
attached with the --remove-empty-files option to patch.
hth,
Doug
--
This .signature sanitized for your protection
Index: l
David E. Thiel wrote:
> Or simply use any of the freely available, cleanly licensed and more
> functional alternatives, many of which are written by programmers
> posessing an at least marginal semblance of sanity:
Sorry David, but I'm going to pick on this reply as an example of a more
general c
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 th
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
Perhaps it's implicit somewhere in your stuff, but one thing that I have
not seen mentioned is along the lines of what Mike Makonnen is doing with
his prototype new installer. Namely divorcing the parts of the system that
do the work and the UI.
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=6270
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Mon, 24 Dec 2007, Umar wrote:
Dear Stefan!
Thanks for your reply!
touch /var/db/pkg/squid-/+IGNOREME.
I already done that. But its not working,
Wesley is correct that he's brought this to my attention already, and also
correct that
Jo Rhett wrote:
> On Nov 11, 2007, at 2:59 PM, Doug Barton wrote:
>> This is very interesting stuff, but I don't see how it would be useful
>> to a very wide audience. My feeling is that the vast majority of our
>> users build and/or install ports as root, and I don&#x
Aryeh Friedman wrote:
> the orginal question is due to a PR I will be filing as soon I have
> a working browser on the machine in question... the PR is that if
> you install libtool-1.5 under 8-current (amd64 only???) it will
> incorrectly ID the installed OS and give errors about "freebsd-"
> not
Naram Qashat wrote:
> I had a question regarding what to do in a port Makefile when the port
> has multiple configuration files to install into PREFIX/etc. I read in
> the Porters Handbook about having to add entries into the Makefile and
> pkg-plist, but that seems to only be good for ports with
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Howdy!
I'm very happy to say that I have a shiny new version of portmaster
available for testing. There are a couple of nice new features, but
more importantly the code has been totally reorganized, and in several
cases totally rewritten. I am al
Naram Qashat wrote:
> Doug Barton wrote:
>> Naram Qashat wrote:
>>> I had a question regarding what to do in a port Makefile when the port
>>> has multiple configuration files to install into PREFIX/etc. I read in
>>> the Porters Handbook about having to add e
slunky wrote:
> Will you please update this port to the latest version (I believe it is 0.32
> from the Warsow website) The version in ports is only 0.12, and it will not
> allow me to play online or over LAN without the latest version.
Giving it a go yourself would get the update done that much
Ok, the SU_CMD stuff is finally done! This turned out to be a little
tougher than I thought, for reasons I'll explain below. First a bug
report.
Doug Barton wrote:
> This is a long message, so if you want to jump into using the new
> version that's fine, but before you do anything
... and of course I forgot the URL, sorry.
http://dougbarton.us/portmaster
Doug
--
This .signature sanitized for your protection
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, s
I'm going to try to combine your two posts so that I can answer in one,
my apologies if I scramble something.
Paul Schmehl wrote:
Some of this has been discussed ad infinitum, but, in an off-list
conversation, I came up with this list of suggested improvements for
port. I'd like to see these
Dominic Fandrey wrote:
Paul Schmehl wrote:
1) You can't build a dependent port and first set the config for the
options that you want. So, when you select sasl in postfix, you never
get the chance to check the saslauthd option, for example.
As the ports man page states:
# make config-recursi
Paul Schmehl wrote:
--On January 11, 2008 9:24:36 PM -0800 Doug Barton <[EMAIL PROTECTED]>
wrote:
First, thanks for you answer. Second, a clarification. I started this
thread from the viewpoint of a port maintainer (I maintain about 10
ports) who is concerned about confusing
RW wrote:
Whilst this is a little irritating, and it would be nice to have it
fixed, in practice it's not all that much of a problem.
I didn't say it was. I just want to be sure that people understand the
limitations of config-recursive, and at worst that they offer the same
suggestion you
Chuck Swiger wrote:
> You should definitely set NO_CDROM and probably NO_PACKAGE, as creating
> a package would be making a derivative work.
You would actually be better off contacting the author and asking them
how they define "derivative work."
Doug
--
This .signature sanitized for you
Tim Clewlow wrote:
Hello,
If I do "make package-recursive" on a port then it first tries to install the
port. This causes it to fail if the port is already installed. However, if I
deinstall the port, and then make package-recursive, it installs the port,
makes the port package, and (this is the
Kris Kennaway wrote:
I still don't understand what you claim is the problem :) We do not
specially update packages like perl; rather, *every* package is
frequently rebuilt and updated.
If I understood the question correctly, I think the OP is asking about
the frequency of rebuilding package
[EMAIL PROTECTED] wrote:
Hello,
I have a server with round about 200 installed Ports. I need
to setup a second server with the same, but slightly newer,
ports recompiled from source.
Is there an easy way to crate a port list with compile options
and feed a build command on the second server wit
hideo wrote:
If I run portmaster with the -a switch it now attempts to rebuild all
installed ports rather than just those that need to be updated.
It doesn't do that for me. Are you sure that you didn't use the -f
switch as well? Or do you perhaps have FORCE=yes in /etc/portmaster.rc
or ~/.p
On Sat, 26 Jan 2008, Aryeh M. Friedman wrote:
Sergey Matveychuk wrote:
Hi!
After a long time, I've got a little free time and spent it working for
portupgrade.
A new version (2.4.0) was released.
Congrats on both the new version, and finding the time. :)
This breaks certain ports (portupgr
hideo wrote:
> I think you're right. -aG and -ai work as expected. Using -i and -G
> together produces the behavior.
Just to confirm, Zach and I worked this out in private e-mail as well,
and that is indeed the problem. I have a fix for the -aiG case, I just
need to test it for other cases as w
Mark Ovens wrote:
> Apologies if this appears twice, I posted it nearly 24 hours ago and it
> hasn't shown up in the list so I'm resending it.
I didn't see the first one, so it probably didn't hit the list.
Both of your problems are almost certainly caused by running the old
version first. Please
Mark Ovens wrote:
> Doug Barton wrote:
>> I didn't see the first one, so it probably didn't hit the list.
>>
>> Both of your problems are almost certainly caused by running the old
>> version first. Please repeat your -Baud run to make sure that
>> portma
Clement Laforet wrote:
WITH_BERKELEYDB is now deprecated in favor of WITH_BDB in order to
make BDB support consistent with the rest of the ports tree.
Is there a warning generated for users that have the old one defined? If
not it would be a good idea to add one. In the past when I've changed
N.J. Mann wrote:
> Good morning,
>
>
> I am using portmaster v2.0 and very good it is to, except...
>
> This morning among the ports that needed updating following my
> over-night CVSup was security/sudo (1.6.9.6 -> 1.6.9.12). I am using
> portmaster's new feature SU_CMD. I am also using the n
Mark Ovens wrote:
Doug, it's happened again:
It's impossible for me to debug this properly without knowing the
command line options you used. I'm guessing from your description of the
problem that you used at least -r and -u.
It honoured the +IGNOREME during the recursive ``make config'' bu
Mark Ovens wrote:
If I understand the problem correctly, the attached patch will fix it.
Please confirm this for me when you can.
That fixed it Doug - thanks for the quick response.
Good news, thanks for testing it.
Doug
--
This .signature sanitized for your protection
___
I'm going to respond to these from the portmaster perspective to try
and give some additional context. No criticism of portupgrade is
intended, since I've said many times that they are not completely
overlapping in feature sets.
I'm also responding since I think these are interesting questions and
Aryeh M. Friedman wrote:
> Doug Barton wrote:
> The idea is more along the lines of knowing how far you are away from
> completing the whole build
... and I repeat my thesis that what you're really interested in is
how much time is left, not how many ports are left to build, and no
Miroslav Lachman wrote:
> Hi,
>
> I am trying to use portmaster to replace installed GnuPG 2 with GnuPG 1.
> portmaster -o security/gnupg1 gnupg-2.0.4
>
> But it always ends with gnupg-2.0.4 re-installed again, so now I have
> both versions installed. Is it possible to use portmaster for this tas
Peter Olsson wrote:
I just did my first big upgrade with portmaster (version 2.1).
Most of the upgrades went well, but I have two problems.
1. Is it possible to get portmaster to accept a conflicting port
instead of the dependency port?
Yes, if both ports have proper CONFLICTS lines. Fortun
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
A user pointed out to me that on the project ideas page the following
entry remains:
Write a new utility for the pkg_install suite, possibly named
pkg_upgrade(1), implementing a subset of existing portupgrade
functionality. The required fun
On Thu, 20 Mar 2008, Michel Talon wrote:
Doug Barton wrote:
So, I renew my inquiry. :) Is portmaster a suitable candidate to fulfill
the role of the utility described, and if not, why not?
At the risk of being flamed,
I certainly hope not. :)
i would venture to say that such an utility
Michel Talon wrote:
> On Thu, Mar 20, 2008 at 01:05:27AM -0700, Doug Barton wrote:
>> On Thu, 20 Mar 2008, Michel Talon wrote:
>>
>>> Doug Barton wrote:
>>> i would venture to say that such an utility
>>> should be able to upgrade things based of *b
David Wolfskill wrote:
> On Thu, Mar 20, 2008 at 01:05:27AM -0700, Doug Barton wrote:
>> ...
>>> One of the
>>> requirements of an upgrade system is predictability, this can only
>>> be achieved by using binary packages.
>> You gain a certain amount of fl
Sean C. Farley wrote:
> On Thu, 20 Mar 2008, Doug Barton wrote:
>
>> On Thu, 20 Mar 2008, Michel Talon wrote:
>>
>>> In my opinion, an example of a correct "pkg_upgrade" type programm
>>> written in C++ is the Debian apt-get. It works predictabl
Sean C. Farley wrote:
>BTW, I think the +IGNOREME files for portmaster should be
>in /var/db/ports, so they may traverse a manual pkg_delete && make
>install.
I'm ambivalent about that, since the way I personally tend to use
+IGNOREME is to avoid dealing with something till I'm ready t
Pav Lucistnik wrote:
> Doug Barton píe v c(t 20. 03. 2008 v 01:05 -0700:
>> On Thu, 20 Mar 2008, Michel Talon wrote:
>>
>>> i would venture to say that such an utility
>>> should be able to upgrade things based of *binary* packages, and
>>> consequently t
Peter Olsson wrote:
> TMPDIR doesn't seem to be set at all, I don't have it in "set".
> Shell is bash.
Ok.
> Here is /etc/make.conf if that is relevant:
> WITHOUT_X11=yes
> WITHOUT_GUI=yes
I would try commenting these two out and see what happens.
> # added by use.perl 2008-01-13 14:50:56
> PE
Peter Olsson wrote:
However, I noticed now that this server has an old bash, bash-2.05b.007_6.
I did a portmaster -o shells/bash bash-2.05b.007_6 and now upgrade of
tk works fine!
Hrrrm, that's weird since portmaster uses only /bin/sh, but I'm glad
it is working for you now. :)
Doug
--
Lars Stokholm wrote:
First of all, I love portmaster. :)
Thanks. :)
Second, I did a "portmaster -e docbook-*" and since it finished
successfully, I expected it had deleted all of my docbook ports, but it
hadn't. From what I could see it had just deleted the first match.
Shouldn't it delete
Willy Picard wrote:
Hi,
I would like to know if there is a smart way to ask portmaster to ignore BROKEN
ports. Currently I added a +IGNOREME file to all BROKEN ports I have but I would
like portmaster to automatically ignore these ports without the +IGNOREME file.
Sorry, portmaster hasn't deve
Lars Stokholm wrote:
Apart from doing 'rm -r /var/db/ports/*' is there a way of cleaning the
folder of stale folders and files?
Not an automated one, no. It would also be somewhat difficult (although
not impossible) to write an automated tool to do it because of the loose
relationship between
Willy Picard wrote:
portupgrade simply ignores BROKEN ports during a "portupgrade -a". I am not even
asking about a similar behaviour for portmaster. I wanted just to ask if an
option allows to do the same. If no such an option exists, I think that its
addition to the functionality of portmaster
Daniel Roethlisberger wrote:
Of course the user wants to be notified of all ports which cannot be
upgraded for some reason (broken, marked BROKEN, removed/missing origin,
etc.), but forcing the upgrade to abort because of a problem with a
single port does not make sense.
It may not make sense
Roman Divacky wrote:
On Wed, Mar 26, 2008 at 05:18:29PM +0100, Pav Lucistnik wrote:
You might have noticed a thread on the mailing list called "ports system
woes". The submitter pointed out an inefficiency in pkg_delete routine,
that parses the whole /var/db/pkg over and over again for every
dep
Roman Divacky wrote:
there are 3 style-only changes in the patch.. 3 lines.. I didnt consider
to make two separate patches for testing/review :)
I'll do it if you insist
Think of it as good practice. :) Seriously though, it does make the
CVS history a little easier to examine. Your best
Dominic Fandrey wrote:
Yesterday I updated OpenOffice and now whenever I run portmaster -Da it
reinstalls it for no reason I can see.
Well it doesn't decide to do things for no reason. :) Somehow it
believes that there is a newer version. What does 'portmaster -L' say?
(Just the part about op
Dominic Fandrey wrote:
Doug Barton wrote:
Dominic Fandrey wrote:
Yesterday I updated OpenOffice and now whenever I run portmaster -Da
it reinstalls it for no reason I can see.
Well it doesn't decide to do things for no reason. :) Somehow it
believes that there is a newer version. What
Miroslav Lachman wrote:
How can I reinstall just one port without version change?
Use it without any flags. Portmaster does by default what portupgrade
does with the -f switch. You're right it should probably be more clear
in the man page that this is the default behavior. I'm not sure how to
Aryeh M. Friedman wrote:
I have brought a older port maintained by [EMAIL PROTECTED] to the
current version I have done all the work needed to make it
committable I have several questions first:
1. How do I take maintainership of the port?
Just change it in the Makefile. Users who sh
Paul Schmehl wrote:
--On Tuesday, June 03, 2008 13:19:37 +0100 RW
<[EMAIL PROTECTED]> wrote:
On Mon, 02 Jun 2008 22:13:15 -0500
Paul Schmehl <[EMAIL PROTECTED]> wrote:
Imagine my surprise when I discovered that *all* of my startup
scripts=20 were running double flags!
So, I looked at /etc/
Miroslav Lachman wrote:
I am almost new to portmaster, so I got a question - is there any
possibility to restart installed services as in portupgrade with defined
BEFOREBUILD / BEFOREDEINSTALL / AFTERINSTALL? Or is there any future
plan to do so? It is annoying if I end up with some dead servic
Jeremy Messenger wrote:
On Wed, 04 Jun 2008 16:22:56 -0500, Doug Barton <[EMAIL PROTECTED]> wrote:
Miroslav Lachman wrote:
And last question - /etc/portmaster.rc - is it realy right place
according to man hier? I would expect it in
/usr/local/etc/portmaster.rc.
You're absolute
Kris Kennaway wrote:
The new 'make describe' target runs entirely using shell
builtins apart from the need to sed pkg-descr to extract the WWW [2]
[2] Actually I am not happy with this but couldn't think of a way to do
it better. Having to fork the subshell costs about 60 seconds of system
Alex Kozlov wrote:
Good idea. I also do something like that [1]. But before we can use this
method, we have to fix ports with bad pkg-descr:
Yeah, in a brief glance at Kris' sed routines I would think at least
some of this work would have to be done no matter what (and it should be
done anyw
Angelo Turetta wrote:
I'm evaluating portmaster: I cannot find an option to use pre-built
packages for upgrading.
At this time there is no such option, and I haven't been able to carve
out the time to work on it. I noted in your message that you've
already discovered the -g option. For your p
Paul Horechuk wrote:
I recently did a source upgrade from FreeBSD 6.3 to FreeBSD 7 Stable. I have
over 1000 ports to recompile so it is taking time.
The recommended procedure for upgrading major branches is to wipe out
all of your ports, then build again from scratch. I know that you said
you
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
To all portmaster users:
My apologies for the version number churn the last week or so. I'm
pretty sure that I can give an "all clear" for version 2.5, and that
both the globbing features and the old features should work as
expected now.
For th
---
www/firefox3: Update to 3.0 final
---
The bsd.gecko.mk has been moved from www/mozilla/ to Mk/. You no longer
need to include bsd.gecko.mk/Makefile.common by manual. We still keep it
in
Kris Kennaway wrote:
Unfortunately it doesn't DTRT with files terminated with DOS-style CRLF
(e.g. devel/p5-Tie-Restore, others).
First, I certainly would not have any problem with a policy that says
files in ports shouldn't have CRLF line endings. Second, I am sure we
could probably do some
Alex Dupre wrote:
Peter Jeremy wrote:
Firstly, I have jdk-1.5.0.14p8,1 installed and this needs updating.
portmaster has decided that doing so requires java/diablo-jdk15 to be
installed - which is wrong because I already have a suitable jdk
installed.
You are right, but the port has the follow
Dominic Fandrey wrote:
Doug Barton wrote:
Portmaster uses CONFLICTS to avoid this issue. This isn't the first
time I've heard this complaint about the java ports. I'm wondering if
glewis could shed some light on why they don't have proper CONFLICTS set.
Because they
901 - 1000 of 1534 matches
Mail list logo
