date:20100806

I've been using ports-mgmt/portupgrade pretty much ever since it
started to exist. Unfortunately portupgrade seems to be pretty much
"abandonware" so I've been told to move on to portmaster. Despite the
very long manpage I can't seem to be able to achieve the following
thing with portmaster:

$ portupgrade --batch -a

If I issue this command I know exactly that I can go out, have a
drink, cook some dinner and unlock my workstation the next day and
find that everything completed unless a port failed to build. With
portmaster I get asked a s*t load of interactive questions, whether I
want to delete some package, whether it's really okay to pull in all
the dependencies and so on.

Can someone spoonfeed me the command I need to issue with portmaster
in order to achieve the same thing as with

$ portupgrade --batch -a

Is that even possible?

$ portupgrade --batch -a

Thanks in advance!

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On 08/06/2010 00:24, Sandra Kachelmann wrote:
> I've been using ports-mgmt/portupgrade pretty much ever since it
> started to exist. Unfortunately portupgrade seems to be pretty much
> "abandonware" so I've been told to move on to portmaster. Despite the
> very long manpage I can't seem to be able to achieve the following
> thing with portmaster:
> 
> $ portupgrade --batch -a

Someone who has used portupgrade and is familiar with exactly what
--batch does can probably help you with that bit, but I'm sure by now
you've figured out that portmaster has a -a feature.

Meanwhile, go get a $BEVERAGE, get comfortable, and actually _read_ the
portmaster man page, don't just skim through it. I put a lot of effort
into explain what portmaster does, how it does it, and also WHY it does
things the way it does. Most (if not all) of your questions are answered
there.

> If I issue this command I know exactly that I can go out, have a
> drink, cook some dinner and unlock my workstation the next day and
> find that everything completed unless a port failed to build.

You should be able to accomplish this with portmaster.


hth,

Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread Alex Kozlov

On 08/06/2010 00:24, Sandra Kachelmann wrote:
> I've been using ports-mgmt/portupgrade pretty much ever since it
> started to exist. Unfortunately portupgrade seems to be pretty much
> "abandonware" so I've been told to move on to portmaster. Despite the
> very long manpage I can't seem to be able to achieve the following
> thing with portmaster:
> $ portupgrade --batch -a
Try echo BATCH?=yes >>/etc/make.conf && portmaster --no-confirm -a


--
Adios
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 10:06 AM, Doug Barton  wrote:
> On 08/06/2010 00:24, Sandra Kachelmann wrote:
>> I've been using ports-mgmt/portupgrade pretty much ever since it
>> started to exist. Unfortunately portupgrade seems to be pretty much
>> "abandonware" so I've been told to move on to portmaster. Despite the
>> very long manpage I can't seem to be able to achieve the following
>> thing with portmaster:
>>
>> $ portupgrade --batch -a
>
> Someone who has used portupgrade and is familiar with exactly what
> --batch does can probably help you with that bit, but I'm sure by now
> you've figured out that portmaster has a -a feature.
>
> Meanwhile, go get a $BEVERAGE, get comfortable, and actually _read_ the
> portmaster man page, don't just skim through it. I put a lot of effort
> into explain what portmaster does, how it does it, and also WHY it does
> things the way it does. Most (if not all) of your questions are answered
> there.

Please don't take this wrong but IMO it's way too overdocumented for
normal users that don't actually read bsd.ports.mk before breakfast
:-)

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: libvpx-0.9.1 doesn't seem to want to compile on current.

"Sergey V. Dyatko"  writes:

> A>> ===> libvpx-0.9.1 depends on file: /usr/local/bin/perl5.10.1 - found
> A>> sed:
> A>> 
> /usr/ports/multimedia/libvpx/work/libvpx-0.9.1/build/make/armlink_adapter.sh:#!/bin/bash:
> A>> No such file or directory
> A>> *** Error code 1
> A>

> A>Can it be related to bsdgrep issue with `-l' option fixed
> A>in /h...@r210479 ?
> A>
>
> [quote]
>  
> /usr/ports/multimedia/libvpx/work/libvpx-0.9.1/build/make/armlink_adapter.sh:#!/bin/bash:
>  No such file or directory
> [/quote]

Doh, you obviously haven't looked at the commit. That bug breaks
following line

@${GREP} -Rl '^#!/bin/bash' ${WRKSRC} |${XARGS} ${REINPLACE_CMD} \
-e 's,#!/bin/bash,#!${LOCALBASE}/bin/bash,g'

And I can easily reproduce it on /h...@r210478.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: libvpx-0.9.1 doesn't seem to want to compile on current.

2010-08-06 Thread Sergey V. Dyatko

On Fri, 06 Aug 2010 13:51:01 +0400
Anonymous  wrote:

> "Sergey V. Dyatko"  writes:
> 
> > A>> ===> libvpx-0.9.1 depends on file: /usr/local/bin/perl5.10.1 -
> > A>> found sed:
> > A>> 
> > /usr/ports/multimedia/libvpx/work/libvpx-0.9.1/build/make/armlink_adapter.sh:#!/bin/bash:
> > A>> No such file or directory
> > A>> *** Error code 1
> > A>
> 
> > A>Can it be related to bsdgrep issue with `-l' option fixed
> > A>in /h...@r210479 ?
> > A>
> >
> > [quote]
> >  
> > /usr/ports/multimedia/libvpx/work/libvpx-0.9.1/build/make/armlink_adapter.sh:#!/bin/bash:
> >  No such file or directory
> > [/quote]
> 
> Doh, you obviously haven't looked at the commit. That bug breaks
> following line
> 
>   @${GREP} -Rl '^#!/bin/bash' ${WRKSRC} |${XARGS}
> ${REINPLACE_CMD} \ -e 's,#!/bin/bash,#!${LOCALBASE}/bin/bash,g'
> 

ooops, I didn't look attentively at Makefile, sorry for the noice :)

> And I can easily reproduce it on /h...@r210478.



-- 
wbr, tiger
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread jhell

On 08/06/2010 04:58, Sandra Kachelmann wrote:
> On Fri, Aug 6, 2010 at 10:06 AM, Doug Barton  wrote:
>> On 08/06/2010 00:24, Sandra Kachelmann wrote:
>>> I've been using ports-mgmt/portupgrade pretty much ever since it
>>> started to exist. Unfortunately portupgrade seems to be pretty much
>>> "abandonware" so I've been told to move on to portmaster. Despite the
>>> very long manpage I can't seem to be able to achieve the following
>>> thing with portmaster:
>>>
>>> $ portupgrade --batch -a
>>
>> Someone who has used portupgrade and is familiar with exactly what
>> --batch does can probably help you with that bit, but I'm sure by now
>> you've figured out that portmaster has a -a feature.
>>
>> Meanwhile, go get a $BEVERAGE, get comfortable, and actually _read_ the
>> portmaster man page, don't just skim through it. I put a lot of effort
>> into explain what portmaster does, how it does it, and also WHY it does
>> things the way it does. Most (if not all) of your questions are answered
>> there.
> 
> Please don't take this wrong but IMO it's way too overdocumented for
> normal users that don't actually read bsd.ports.mk before breakfast
> :-)
> 
> Sandra

I have done exactly what you want with (portmaster -a), albeit you
should sit there and wait for any option screens to pop up until you
leave but it can be done. But also see below.

Doug,

One fallback that I cannot seem to get over is the creation of a backup
package failed do you want to ignore [i] message prompt & the package
messages that are displayed with $PAGER at the end of the upgrades.  I
do not recall the packages that his had happened on, it does not happen
often but when it did happen it was just before a nice long compile of
OpenOffice :( while I was gone.

The pkg-message problem has been stumping me since it inhibits my use of
pwait(1) on another terminal. For instance I started a portmaster -a on
one terminal and issued pwait(1) on another so I could build a new
kernel and world right after a ports(7) upgrade. Since the pkg-message
is displayed with PAGER obviously the initial portmaster process never
terminates and post processes are revolving so they would/could exit to
soon.

Do not prompt for a backup package creation failure and force creation
of whatever you have on the system already?

Configuration option to email the output of upgraded packages and their
pkg-message or a similar option to just log to a file?

Also I still see a need for installing a
/usr/local/etc/portmaster.rc.sample file for whatever version is
installed and seperating that from the man page. This would make it much
easier on the end user to configure portmaster for options they see fit.

Forwarded apologies if any of this is confusing.

Regards,

-- 

On another note I wish wc(1) would output some headers above these. ;)

$ man portmaster |wc -Lclmw
  6103363   30764 187

 jhell,v

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ports/149264: Update port: devel/p5-ParseLex

2010-08-06 Thread pirzyk

Synopsis: Update port: devel/p5-ParseLex

Responsible-Changed-From-To: pirzyk->freebsd-ports
Responsible-Changed-By: pirzyk
Responsible-Changed-When: Fri Aug 6 12:00:34 UTC 2010
Responsible-Changed-Why: 
Approve diff, please commit.  Thanks


http://www.freebsd.org/cgi/query-pr.cgi?pr=149264
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread Martin Schweizer

Hello Sandra

I was in a similar situation. I found the following paramters very usefull:

portmaster -a -d --no-confirm

-a: Take all installed ports
-d: Delete any dependicies
-no--confirm: Wait not after the check which ports are upgradable

With the above switch portmaster waits in two case:
1. If you run in an compile error
2. If the port is new and will asks you about make config

I did now three upgrades like above and it worked as expected.

Regards,



2010/8/6 Sandra Kachelmann :
> On Fri, Aug 6, 2010 at 10:06 AM, Doug Barton  wrote:
>> On 08/06/2010 00:24, Sandra Kachelmann wrote:
>>> I've been using ports-mgmt/portupgrade pretty much ever since it
>>> started to exist. Unfortunately portupgrade seems to be pretty much
>>> "abandonware" so I've been told to move on to portmaster. Despite the
>>> very long manpage I can't seem to be able to achieve the following
>>> thing with portmaster:
>>>
>>> $ portupgrade --batch -a
>>
>> Someone who has used portupgrade and is familiar with exactly what
>> --batch does can probably help you with that bit, but I'm sure by now
>> you've figured out that portmaster has a -a feature.
>>
>> Meanwhile, go get a $BEVERAGE, get comfortable, and actually _read_ the
>> portmaster man page, don't just skim through it. I put a lot of effort
>> into explain what portmaster does, how it does it, and also WHY it does
>> things the way it does. Most (if not all) of your questions are answered
>> there.
>
> Please don't take this wrong but IMO it's way too overdocumented for
> normal users that don't actually read bsd.ports.mk before breakfast
> :-)
>
> Sandra
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>



-- 
Martin Schweizer
schweizer.mar...@gmail.com
Tel.: +41 32 512 48 54 (VoIP)
Fax: +1 619 3300587
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer
 wrote:
> Hello Sandra
>
> I was in a similar situation. I found the following paramters very usefull:
>
> portmaster -a -d --no-confirm
>
> -a: Take all installed ports
> -d: Delete any dependicies
> -no--confirm: Wait not after the check which ports are upgradable
>
> With the above switch portmaster waits in two case:
> 1. If you run in an compile error
> 2. If the port is new and will asks you about make config
>
> I did now three upgrades like above and it worked as expected.

Hi Martin

Thank you for your answer (and everyone else who replied). This is
exactly the reason why I keep going back to portupgrade. Default
OPTIONS almost always work for me - if not I go to the ports directory
and run make config then let the --batch option of portinstall deal
with everything.

It would be extremely nice if there would be a --batch option that
would act like portupgrade.

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread RW

On Fri, 6 Aug 2010 14:44:09 +0200
Sandra Kachelmann  wrote:

> It would be extremely nice if there would be a --batch option that
> would act like portupgrade.

Does setting BATCH in the environment not work?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread David Wolfskill

On Fri, Aug 06, 2010 at 01:52:40PM +0200, Martin Schweizer wrote:
> Hello Sandra
> 
> I was in a similar situation. I found the following paramters very usefull:
> 
> portmaster -a -d --no-confirm
> 
> -a: Take all installed ports
> -d: Delete any dependicies

Errr...  careful, there:

 -d  always clean distfiles

Not quite the same thing.  :-}

> -no--confirm: Wait not after the check which ports are upgradable
> ...

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpjfd9aiyyJ4.pgp
Description: PGP signature

Re: i keep trying to move from portupgrade to portmaster

> On Fri, Aug 6, 2010 at 2:44 PM, Sandra Kachelmann 
>  wrote:
> > On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer
> >  wrote:
> >> Hello Sandra
> >>
> >> I was in a similar situation. I found the following paramters very usefull:
> >>
> >> portmaster -a -d --no-confirm
> >>
> >> -a: Take all installed ports
> >> -d: Delete any dependicies
> >> -no--confirm: Wait not after the check which ports are upgradable
> >>
> >> With the above switch portmaster waits in two case:
> >> 1. If you run in an compile error
> >> 2. If the port is new and will asks you about make config
> >>
> >> I did now three upgrades like above and it worked as expected.
> >
> > Hi Martin
> >
> > Thank you for your answer (and everyone else who replied). This is
> > exactly the reason why I keep going back to portupgrade. Default
> > OPTIONS almost always work for me - if not I go to the ports directory
> > and run make config then let the --batch option of portinstall deal
> > with everything.
> >
> > It would be extremely nice if there would be a --batch option that
> > would act like portupgrade.
>
> Does setting BATCH in the environment not work?

Unfortunately not. I tried:

$ BATCH=yes portmaster -a -d --no-confirm

and like someone else suggested adding BATCH?=yes to /etc/make.conf,
then running:

$ portmaster -a -d --no-confirm

Still asks me to confirm all the options.

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread Freddie Cash

On Fri, Aug 6, 2010 at 6:26 AM, Sandra Kachelmann
 wrote:
>> On Fri, Aug 6, 2010 at 2:44 PM, Sandra Kachelmann 
>>  wrote:
>> > On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer
>> >  wrote:
>> >> Hello Sandra
>> >>
>> >> I was in a similar situation. I found the following paramters very 
>> >> usefull:
>> >>
>> >> portmaster -a -d --no-confirm
>> >>
>> >> -a: Take all installed ports
>> >> -d: Delete any dependicies
>> >> -no--confirm: Wait not after the check which ports are upgradable

> and like someone else suggested adding BATCH?=yes to /etc/make.conf,
> then running:
>
> $ portmaster -a -d --no-confirm
>
> Still asks me to confirm all the options.

If you absolutely do not want to see the OPTIONS screens, no matter
what, then add -G (see man page for details).


-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 3:38 PM, Freddie Cash  wrote:
> On Fri, Aug 6, 2010 at 6:26 AM, Sandra Kachelmann
>  wrote:
>>> On Fri, Aug 6, 2010 at 2:44 PM, Sandra Kachelmann 
>>>  wrote:
>>> > On Fri, Aug 6, 2010 at 1:52 PM, Martin Schweizer
>>> >  wrote:
>>> >> Hello Sandra
>>> >>
>>> >> I was in a similar situation. I found the following paramters very 
>>> >> usefull:
>>> >>
>>> >> portmaster -a -d --no-confirm
>>> >>
>>> >> -a: Take all installed ports
>>> >> -d: Delete any dependicies
>>> >> -no--confirm: Wait not after the check which ports are upgradable
>
>> and like someone else suggested adding BATCH?=yes to /etc/make.conf,
>> then running:
>>
>> $ portmaster -a -d --no-confirm
>>
>> Still asks me to confirm all the options.
>
> If you absolutely do not want to see the OPTIONS screens, no matter
> what, then add -G (see man page for details).

I tried that but if i run

$ portmaster --no-confirm -G /usr/ports/x11/xorg

The libiconv OPTIONS dialog pops up.

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More  wrote:
> On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash  wrote:
>>
>> If you absolutely do not want to see the OPTIONS screens, no matter
>> what, then add -G (see man page for details).
>
> No, that's not what -G does.  -G makes portmaster handle the options screen
> similar to portupgrade eg waiting to ask you until it runs into it.
>
> Setting BATCH=yes in make.conf does work, maybe BATCH?=yes breaks it, my
> make.conf fu is only sightly better than it documentation which isn't much.
>
> --
> Adam Vande More

OK, that does work:

Setting BATCH=yes in /etc/make.conf and running:

$ portmaster --no-confirm -G /usr/ports/x11/xorg

But is there really no way to specify it as argument of portmaster?

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 3:59 PM, Sandra Kachelmann
 wrote:
> On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More  wrote:
>> On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash  wrote:
>>>
>>> If you absolutely do not want to see the OPTIONS screens, no matter
>>> what, then add -G (see man page for details).
>>
>> No, that's not what -G does.  -G makes portmaster handle the options screen
>> similar to portupgrade eg waiting to ask you until it runs into it.
>>
>> Setting BATCH=yes in make.conf does work, maybe BATCH?=yes breaks it, my
>> make.conf fu is only sightly better than it documentation which isn't much.
>>
>> --
>> Adam Vande More
>
> OK, that does work:
>
> Setting BATCH=yes in /etc/make.conf and running:
>
> $ portmaster --no-confirm -G /usr/ports/x11/xorg
>
> But is there really no way to specify it as argument of portmaster?
>
> Sandra

Think I found it:

portmaster --no-confirm -G -m 'BATCH=yes' /usr/ports/x11/xorg

This seems to do what I want. Still --batch would be nice - guess I'll
create a shell alias.

Sorry for all the lame questions - it seems that I want something
really special nobody else is interested in.

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread Matthias Andree

Am 06.08.2010 15:59, schrieb Sandra Kachelmann:
> On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More  wrote:
>> On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash  wrote:
>>>
>>> If you absolutely do not want to see the OPTIONS screens, no matter
>>> what, then add -G (see man page for details).
>>
>> No, that's not what -G does.  -G makes portmaster handle the options screen
>> similar to portupgrade eg waiting to ask you until it runs into it.
>>
>> Setting BATCH=yes in make.conf does work, maybe BATCH?=yes breaks it, my
>> make.conf fu is only sightly better than it documentation which isn't much.
>>
>> --
>> Adam Vande More
> 
> OK, that does work:
> 
> Setting BATCH=yes in /etc/make.conf and running:
> 
> $ portmaster --no-confirm -G /usr/ports/x11/xorg
> 
> But is there really no way to specify it as argument of portmaster?

Did you try this? portmaster ... -mBATCH=yes ...

-- 
Matthias Andree
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash  wrote:

>
> If you absolutely do not want to see the OPTIONS screens, no matter
> what, then add -G (see man page for details).
>

No, that's not what -G does.  -G makes portmaster handle the options screen
similar to portupgrade eg waiting to ask you until it runs into it.

Setting BATCH=yes in make.conf does work, maybe BATCH?=yes breaks it, my
make.conf fu is only sightly better than it documentation which isn't much.

-- 
Adam Vande More
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

keep-alive option for sudo in portmaster

While updating ports some take a long time to compile and when it
finally comes time to install I need to type password again.
Is there an option to prevent that? Smth like running

  $ sudo true

would be enough to update time stamp. They're per tty by default, anyway.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 4:09 PM, Sandra Kachelmann
 wrote:
> On Fri, Aug 6, 2010 at 3:59 PM, Sandra Kachelmann
>  wrote:
>> On Fri, Aug 6, 2010 at 3:45 PM, Adam Vande More  
>> wrote:
>>> On Fri, Aug 6, 2010 at 8:38 AM, Freddie Cash  wrote:

 If you absolutely do not want to see the OPTIONS screens, no matter
 what, then add -G (see man page for details).
>>>
>>> No, that's not what -G does.  -G makes portmaster handle the options screen
>>> similar to portupgrade eg waiting to ask you until it runs into it.
>>>
>>> Setting BATCH=yes in make.conf does work, maybe BATCH?=yes breaks it, my
>>> make.conf fu is only sightly better than it documentation which isn't much.
>>>
>>> --
>>> Adam Vande More
>>
>> OK, that does work:
>>
>> Setting BATCH=yes in /etc/make.conf and running:
>>
>> $ portmaster --no-confirm -G /usr/ports/x11/xorg
>>
>> But is there really no way to specify it as argument of portmaster?
>>
>> Sandra
>
> Think I found it:
>
> portmaster --no-confirm -G -m 'BATCH=yes' /usr/ports/x11/xorg
>
> This seems to do what I want. Still --batch would be nice - guess I'll
> create a shell alias.
>
> Sorry for all the lame questions - it seems that I want something
> really special nobody else is interested in.

Hmm...

I just tried to update an outdated system with:

$ portmaster --no-confirm -G -m 'BATCH=yes' -a

after a while it asked me whether I want to delete pcre - so -m
BATCH=yes does not work.

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 9:28 AM, Sandra Kachelmann <
s.kachelm...@googlemail.com> wrote:

> Hmm...
>
> I just tried to update an outdated system with:
>
> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>
> after a while it asked me whether I want to delete pcre - so -m
> BATCH=yes does not work.
>

Come on, please read the man page.

-- 
Adam Vande More
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread Freddie Cash

On Fri, Aug 6, 2010 at 7:28 AM, Sandra Kachelmann
 wrote:
> I just tried to update an outdated system with:
>
> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>
> after a while it asked me whether I want to delete pcre - so -m
> BATCH=yes does not work.

What's the exact message?  Is it asking about deleting old distfiles?
There's an option to always delete (don't ask) and another option to
always ask.  It's -d (just delete the distfile, don't ask) and -D
(always ask before deleting a distfile).

If not, what's the question being asked?

-- 
Freddie Cash
fjwc...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 4:31 PM, Freddie Cash  wrote:
> On Fri, Aug 6, 2010 at 7:28 AM, Sandra Kachelmann
>  wrote:
>> I just tried to update an outdated system with:
>>
>> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>>
>> after a while it asked me whether I want to delete pcre - so -m
>> BATCH=yes does not work.
>
> What's the exact message?  Is it asking about deleting old distfiles?
> There's an option to always delete (don't ask) and another option to
> always ask.  It's -d (just delete the distfile, don't ask) and -D
> (always ask before deleting a distfile).
>
> If not, what's the question being asked?

Here is another one:

...

test -z "/usr/local/share/common-lisp/source/gpg-error" ||
../.././install-sh -c -d
"/usr/local/share/common-lisp/source/gpg-error"
 install  -o root -g wheel -m 444 'gpg-error-codes.lisp'
'/usr/local/share/common-lisp/source/gpg-error/gpg-error-codes.lisp'
cd /usr/ports/security/libgpg-error/work/libgpg-error-1.8 && install
-o root -g wheel -m 444 AUTHORS ChangeLog NEWS README
/usr/local/share/doc/libgpg-error
===>   Running ldconfig
/sbin/ldconfig -m /usr/local/lib
===>   Registering installation for libgpg-error-1.8

===>  Cleaning for libgpg-error-1.8

===>>> Updating dependency entry for libgpg-error-1.8 in each dependent port

===>>> Upgrade of libgpg-error-1.7_1 to libgpg-error-1.8 succeeded

===>>> Delete libgpg-error-1.7.tar.bz2? y/n [n]

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 4:30 PM, Adam Vande More  wrote:
> On Fri, Aug 6, 2010 at 9:28 AM, Sandra Kachelmann
>  wrote:
>>
>> Hmm...
>>
>> I just tried to update an outdated system with:
>>
>> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
>>
>> after a while it asked me whether I want to delete pcre - so -m
>> BATCH=yes does not work.
>
> Come on, please read the man page.

Ignore me if you don't want to help. The man page is too huge.

Sandra
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ports/149264: Update port: devel/p5-ParseLex

2010-08-06 Thread itetcu

Synopsis: Update port: devel/p5-ParseLex

Responsible-Changed-From-To: freebsd-ports->freebsd-ports-bugs
Responsible-Changed-By: itetcu
Responsible-Changed-When: Fri Aug 6 14:43:52 UTC 2010
Responsible-Changed-Why: 
Correct assignment (don't assign to the mailing list).

http://www.freebsd.org/cgi/query-pr.cgi?pr=149264
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: keep-alive option for sudo in portmaster

2010-08-06 Thread Ashish SHUKLA

Anonymous  writes:
> While updating ports some take a long time to compile and when it
> finally comes time to install I need to type password again.
> Is there an option to prevent that? Smth like running

>   $ sudo true

How about using `timestamp_timeout` option in sudoers(5) ? OR maybe using
NOPASSWD in sudoers for that specific command ?

HTH
-- 
Ashish SHUKLA  | GPG: F682 CDCC 39DC 0FEA E116  20B6 C746 CFA9 E74F A4B0
freebsd.org!ashish | http://people.freebsd.org/~ashish/

“If tempted by something that feels "altruistic," examine your motives
and root out that self-deception. Then, if you still want to do it,
wallow in it!” (Robert A. Heinlein, 1973)

pgpW8Ow787mqw.pgp
Description: PGP signature

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread Jim Riggs

On Aug 6, 2010, at 9:28 AM, Sandra Kachelmann wrote:

> Hmm...
> 
> I just tried to update an outdated system with:
> 
> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
> 
> after a while it asked me whether I want to delete pcre - so -m
> BATCH=yes does not work.

Somewhere along the thread you lost your -d.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: keep-alive option for sudo in portmaster

ash...@freebsd.org (Ashish SHUKLA) writes:

> Anonymous  writes:
>> While updating ports some take a long time to compile and when it
>> finally comes time to install I need to type password again.
>> Is there an option to prevent that? Smth like running
>
>>   $ sudo true
>
> How about using `timestamp_timeout` option in sudoers(5) ? OR maybe using
> NOPASSWD in sudoers for that specific command ?

Looking at sudoers(5) it doesn't seem that I can easily use different
settings per tty. And I'm *satisfied* with default timeout.

Increasing timeout or not using password is more insecure than
preventing timestamp from expiring in an isolated tty (screen/tmux).
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread B. Estrade

On Fri, Aug 06, 2010 at 04:37:42PM +0200, Sandra Kachelmann wrote:
> On Fri, Aug 6, 2010 at 4:30 PM, Adam Vande More  wrote:
> > On Fri, Aug 6, 2010 at 9:28 AM, Sandra Kachelmann
> >  wrote:
> >>
> >> Hmm...
> >>
> >> I just tried to update an outdated system with:
> >>
> >> $ portmaster --no-confirm -G -m 'BATCH=yes' -a
> >>
> >> after a while it asked me whether I want to delete pcre - so -m
> >> BATCH=yes does not work.
> >
> > Come on, please read the man page.
> 
> Ignore me if you don't want to help. The man page is too huge.

The man page is not that big, I just checked due to my interest in
this thread. portmaster seems to be very configurable and scriptable,
but I would suggest that among the "examples" in the man page be the
idiom(s) one might want to use if a complete batch process is desired.

Cheers,
Brett

> 
> Sandra
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

-- 
B. Estrade 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

games/connect4 segfaults.

2010-08-06 Thread David DEMELIER

Hi,

I just wanted to try games/connect4 but it segfaults here on FreeBSD
8.1-RELEASE and amd64.

It's a long backtrace so I think you should try it by yourself.

Kind regards.

-- 
Demelier David
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: games/connect4 segfaults.

2010-08-06 Thread Chip Camden

Quoth David DEMELIER on Friday, 06 August 2010:
> Hi,
> 
> I just wanted to try games/connect4 but it segfaults here on FreeBSD
> 8.1-RELEASE and amd64.
> 
> It's a long backtrace so I think you should try it by yourself.
> 
> Kind regards.
> 
> -- 
> Demelier David

seg faults for me, too -- but with no backtrace.  I'm on 8.1-STABLE
amd64.

-- 
Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F
http://camdensoftware.com | http://chipstips.com| http://chipsquips.com


pgpHetOGnfvF4.pgp
Description: PGP signature

Stepping down from my ports

2010-08-06 Thread Frank Steinborn

Dear porters,

unfortunately I need to step down from all the FreeBSD
ports that I currently maintain, namely:

audio/ices0
audio/linux-shoutcast
audio/shoutcast
benchmarks/nbench
devel/libgee
games/avanor
games/crimson
games/wrogue
irc/minbif
misc/apparix
multimedia/gpodder
net-im/pino
net-mgmt/nagios-check_ice
net-mgmt/nagios-check_nick
net-mgmt/nipper
net/p5-Event-tcp
security/py-otr

Sorry - I don't take this easily. I really enjoyed working with the
community but due to a new employment and many other changes in my
life I'm currenty too much under water to find the time to maintain
these.

I don't like stupidly approving patches from people that would be
better maintainers than me anyway...

I will keep maintaining comms/p5-SMS-SMS77 because upstream stopped
development and I heavily depend on this port.

I surely will be back some day picking up a port here and there, but
for now: pleae pick up these small, poor ports and treat them with
love :)

Thanks,
Frank
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: games/connect4 segfaults.

David DEMELIER  writes:

> Hi,
>
> I just wanted to try games/connect4 but it segfaults here on FreeBSD
> 8.1-RELEASE and amd64.
>
> It's a long backtrace so I think you should try it by yourself.

Hmm, I have a very short one here, on gdb71 + gcc45.

  Program received signal SIGSEGV, Segmentation fault.
  0x004031ac in envmesg (environ=0x7fff9550, message=0x4038aa 
) at c4.c:841
  841 *(int *)last = 0;   /* clean out last word */
  (gdb) bt f
  #0  0x004031ac in envmesg (environ=0x7fff9550, message=0x4038aa 
) at c4.c:841
  last = 0xa0fc 
  address = 0x7fff9370 
  #1  0x004011d2 in main (argc=1, argv=0x7fff9360, 
envp=0x7fff9370) at c4.c:60
  move = 1
  square = -27792
  winner = 3
  temp = 8

The pointers seem bogus. I've tried to compile the port with -m32 and it works.
So, it should be marked BROKEN on amd64.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Stepping down from my ports

2010-08-06 Thread Charlie Kester


On Fri 06 Aug 2010 at 11:51:05 PDT Frank Steinborn wrote:


multimedia/gpodder


I can take this one.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On 08/06/2010 04:52, Martin Schweizer wrote:
> Hello Sandra
> 
> I was in a similar situation. I found the following paramters very usefull:
> 
> portmaster -a -d --no-confirm
> 
> -a: Take all installed ports
> -d: Delete any dependicies

That's not what -d means. You would be better off with the option to not
delete any distfiles, along with occasionally running the standalone
feature to clean distfiles.


hth,

Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On 08/06/2010 05:44, Sandra Kachelmann wrote:

> Thank you for your answer (and everyone else who replied). This is
> exactly the reason why I keep going back to portupgrade. Default
> OPTIONS almost always work for me - if not I go to the ports directory
> and run make config then let the --batch option of portinstall deal
> with everything.
> 
> It would be extremely nice if there would be a --batch option that
> would act like portupgrade.

Now that you've been more specific about what you want, I have good news
for you. :)  In the current development version of portmaster I have
revamped the -G option so that it acts more like BATCH=YES in the sense
that it specifically skips all OPTIONS dialogs. Therefore you should be
able to accomplish at least this part of what you want with -G alone,
without using BATCH=YES at all.

I plan to commit the update very soon, hopefully this weekend. I'm
currently doing an extensive code review/whitespace realignment/etc.

hth,

Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On 08/06/2010 04:34, jhell wrote:

> Doug,
> 
> One fallback that I cannot seem to get over is the creation of a backup
> package failed do you want to ignore [i] message prompt & the package
> messages that are displayed with $PAGER at the end of the upgrades.  I
> do not recall the packages that his had happened on, it does not happen
> often but when it did happen it was just before a nice long compile of
> OpenOffice :( while I was gone.
> 
> The pkg-message problem has been stumping me since it inhibits my use of
> pwait(1) on another terminal. For instance I started a portmaster -a on
> one terminal and issued pwait(1) on another so I could build a new
> kernel and world right after a ports(7) upgrade. Since the pkg-message
> is displayed with PAGER obviously the initial portmaster process never
> terminates and post processes are revolving so they would/could exit to
> soon.

To deal with this you can use PAGER=cat, either on the command line, or
you can put it in a portmaster rc file.

> Do not prompt for a backup package creation failure

I need to add an option for this, but it will likely be an "expert"
option that you can set in the rc file. The theory is that package
creation failure should be a rare thing, and since portmaster has no way
to know what packages are really critical to any given system it treats
inability to safely recover from an upgrade failure as a critical error.
However, having the ability to disable this is an oft-requested feature,
I just haven't gotten to it yet.

I actually took a look at the code in this area last night with an eye
towards creating this option, I'll see if I can get it done for the next
release.

> and force creation of whatever you have on the system already?

Not sure what this means, can you explain it in more detail?

> Configuration option to email the output of upgraded packages and their
> pkg-message or a similar option to just log to a file?

The ability to log actions to a file is already in the dev version in
svn. You have to specify PM_LOG in your rc file. I want to see how that
goes first before I consider adding a command line option for it. I
don't anticipate adding e-mail functionality to portmaster, that sounds
like something that should be done in a wrapper script, along with
PM_LOG. (Although, there was a meme from the early days that no Unix app
is complete until it grows the ability to do e-mail, so you never know ...)

> Also I still see a need for installing a
> /usr/local/etc/portmaster.rc.sample file for whatever version is
> installed and seperating that from the man page. This would make it much
> easier on the end user to configure portmaster for options they see fit.

Yeah, I think you're probably right that it's time to do this. The
current system actually makes it easier for me to keep the docs up to
date when I add new options, but maybe if I remove that bit the man page
won't seem so scary. :)

Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Trying to use the USERS and SHAREOWN functionalities

Are there any examples of how to use the USERS functionality together
with the SHAREOWN functionality in a port makefile?  I'm working on
updating the ecartis port to use standard functionality for its user
ID, but can't seem to tell how to make sure that the USERS are created
before files are installed, and that installed files are then owned by
the user that is created.

Thanks,
Jim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: keep-alive option for sudo in portmaster

On 08/06/2010 07:27, Anonymous wrote:
> While updating ports some take a long time to compile and when it
> finally comes time to install I need to type password again.
> Is there an option to prevent that? Smth like running
> 
>   $ sudo true
> 
> would be enough to update time stamp. They're per tty by default, anyway.

While I can sympathize with your situation, I think you'd be better off
in this case running your portmaster commands in an actual root shell.


Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 5:26 PM, Doug Barton  wrote:
> On 08/06/2010 04:34, jhell wrote:
>> Do not prompt for a backup package creation failure
>
> I need to add an option for this, but it will likely be an "expert"
> option that you can set in the rc file. The theory is that package
> creation failure should be a rare thing, and since portmaster has no way
> to know what packages are really critical to any given system it treats
> inability to safely recover from an upgrade failure as a critical error.
> However, having the ability to disable this is an oft-requested feature,
> I just haven't gotten to it yet.
>
>> and force creation of whatever you have on the system already?
>
> Not sure what this means, can you explain it in more detail?

One example I have (unfortunately): I accidentally wiped out
/usr/local/.  Reinstalling all my ports was easy -- first reinstall
portmaster and then run "portmaster -af".  The problem was that for
every single port I had to say "Yes, ignore the fact that the port
wasn't already there".  So I had to tend the process all the way
through.  An option to force ignoring the package creation failure
would allow that to be an unattended process.

Jim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On 08/06/2010 14:33, Jim Trigg wrote:

> One example I have (unfortunately): I accidentally wiped out
> /usr/local/.  Reinstalling all my ports was easy -- first reinstall
> portmaster and then run "portmaster -af".  The problem was that for
> every single port I had to say "Yes, ignore the fact that the port
> wasn't already there".  So I had to tend the process all the way
> through.  An option to force ignoring the package creation failure
> would allow that to be an unattended process.

Too bad you didn't read the man page, as there is already an option to
skip backup package creation altogether. :)


Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 4:26 PM, Doug Barton  wrote:

> I need to add an option for this, but it will likely be an "expert"
> option that you can set in the rc file. The theory is that package
> creation failure should be a rare thing, and since portmaster has no way
> to know what packages are really critical to any given system it treats
> inability to safely recover from an upgrade failure as a critical error.
> However, having the ability to disable this is an oft-requested feature,
> I just haven't gotten to it yet.
>
> I actually took a look at the code in this area last night with an eye
> towards creating this option, I'll see if I can get it done for the next
> release.
>

While your in the mood for for taking portmaster suggestions, I think an
option to backup all currently installed packages would be useful.  I have a
python script that does this for me, but it would be easy enough to use sh
as well.  I do this because there have been too many times something has
broken during a port upgrade run and I need to revert immediately and fix
later.  I realize the backup package feature sort of does the same thing,
but reconciling the pre- and post- updates is a tough thing for me.  Having
a user defined directory all currently installed ports can be put in is much
easier to work with IMO. I know of other people doing similar things because
I shared my script on questions- and got a few responses awhile ago.

-- 
Adam Vande More
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Trying to use the USERS and SHAREOWN functionalities

2010-08-06 Thread Jason


On Fri, Aug 06, 2010 at 05:28:50PM -0400, Jim Trigg thus spake:

Are there any examples of how to use the USERS functionality together
with the SHAREOWN functionality in a port makefile?  I'm working on
updating the ecartis port to use standard functionality for its user
ID, but can't seem to tell how to make sure that the USERS are created
before files are installed, and that installed files are then owned by
the user that is created.


Not sure of examples but if you use 
USERS= me

GROUPS= ${USERS}

When you install, it will first check/install the users. 


If you note:
SHAREOWN=me
SHAREGRP=${SHAREOWN}

It will then install the files with this ownership if you are using the install
macro that use these variables (ie. COPYTREE_SHARE)
 
Take a look at bsd.port.mk. It's all in there.


Hope this helps!



Thanks,
Jim


jgh
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On 08/06/2010 15:03, Adam Vande More wrote:

> While your in the mood for for taking portmaster suggestions,

I am always in the mood for taking suggestions. :)

> I think an
> option to backup all currently installed packages would be useful. 

for pkg in /var/db/pkg/* ; do
pkg_create -b $pkg
done

> I
> have a python script that does this for me, but it would be easy enough
> to use sh as well.  I do this because there have been too many times
> something has broken during a port upgrade run and I need to revert
> immediately and fix later.  I realize the backup package feature sort of
> does the same thing, but reconciling the pre- and post- updates is a
> tough thing for me.  Having a user defined directory all currently
> installed ports can be put in is much easier to work with IMO. I know of
> other people doing similar things because I shared my script on
> questions- and got a few responses awhile ago.

It sounds like you want to add the option(s) for "create and keep a
backup package of an installed port" and/or "create a package of the new
port" either to your command line, wrapper script, or a portmaster rc
file. You could use the command line above to create an up to date
repository of your currently installed packages, and the 2 options above
would both make sure you can back out an update and keep your local
package repo up to date automatically.

In the upcoming portmaster version there is also a new feature to clean
out stale stuff from your $PACKAGES directory similarly to the way the
feature to clean out stale distfiles works now, which should help you in
keeping the repository described above fairly un-crufty.

hth,

Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Stepping down from my ports

2010-08-06 Thread Sahil Tandon

On Fri, 2010-08-06 at 13:16:49 -0700, Charlie Kester wrote:

> On Fri 06 Aug 2010 at 11:51:05 PDT Frank Steinborn wrote:
> >
> >multimedia/gpodder
> 
> I can take this one.

Done.

-- 
Sahil Tandon 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On 08/06/2010 14:03, Doug Barton wrote:
> On 08/06/2010 05:44, Sandra Kachelmann wrote:
> 
>> Thank you for your answer (and everyone else who replied). This is
>> exactly the reason why I keep going back to portupgrade. Default
>> OPTIONS almost always work for me 

In my haste to point out the exciting new update to -G I neglected to
point out how OPTIONS work generally, and more specifically with
portmaster. If you run the current production version of portmaster
without -G then you will be prompted with all of the OPTIONS screens for
all of the ports that need install/updating, then portmaster will start
building stuff and leave you alone till it's done.

On successive builds for the same port you will not be presented with
that OPTIONS dialog again unless the questions have changed (OPTIONS
lines added or deleted). IOW, the ports system "remembers" your choices
so that you don't need to re-answer all the same questions again. In
portmaster this behavior can be influenced with a command line option to
force reconsideration of all OPTIONS.

Also, if you're satisfied with the defaults you should probably consider
the option to try installing packages first, and only build the port if
the package is not up to date.

hth,

Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: keep-alive option for sudo in portmaster

Doug Barton  writes:

> On 08/06/2010 07:27, Anonymous wrote:
>> While updating ports some take a long time to compile and when it
>> finally comes time to install I need to type password again.
>> Is there an option to prevent that? Smth like running
>> 
>>   $ sudo true
>> 
>> would be enough to update time stamp. They're per tty by default, anyway.
>
> While I can sympathize with your situation, I think you'd be better off
> in this case running your portmaster commands in an actual root shell.

Wouldn't periodic hook be useful to smth else besides PM_SU_CMD? Like
sending time passed since current port build started to xterm title.
It may help to guess how long till it completes the build.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: keep-alive option for sudo in portmaster

On 08/06/2010 15:54, Anonymous wrote:
> Doug Barton  writes:
> 
>> On 08/06/2010 07:27, Anonymous wrote:
>>> While updating ports some take a long time to compile and when it
>>> finally comes time to install I need to type password again.
>>> Is there an option to prevent that? Smth like running
>>>
>>>   $ sudo true
>>>
>>> would be enough to update time stamp. They're per tty by default, anyway.
>>
>> While I can sympathize with your situation, I think you'd be better off
>> in this case running your portmaster commands in an actual root shell.
> 
> Wouldn't periodic hook be useful to smth else besides PM_SU_CMD? Like
> sending time passed since current port build started to xterm title.
> It may help to guess how long till it completes the build.

I look forward to reviewing your patches to implement this feature. :)


Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Port stuck in the pipe

2010-08-06 Thread Jesse Smith

About two months ago I submitted a PR for a new port
(http://www.freebsd.org/cgi/query-pr.cgi?pr=147768) 

>From the tracking page it looks like it got bounced around a little and
then didn't go anywhere. It's a game, so I understand it being a low
priority, but I'm wondering if there is anything I can do to help the
process along. Should I just wait it out and hope it gets picked up, or
is there something pro-active I can do?

Thanks,
Jesse




___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: keep-alive option for sudo in portmaster

On Fri, Aug 6, 2010 at 6:58 PM, Doug Barton  wrote:
> On 08/06/2010 15:54, Anonymous wrote:
>> Doug Barton  writes:
>>> While I can sympathize with your situation, I think you'd be better off
>>> in this case running your portmaster commands in an actual root shell.
>>
>> Wouldn't periodic hook be useful to smth else besides PM_SU_CMD? Like
>> sending time passed since current port build started to xterm title.
>> It may help to guess how long till it completes the build.
>
> I look forward to reviewing your patches to implement this feature. :)

I use aliases:

alias portadd="sudo portmaster"
alias portrm="sudo portmaster -e"
alias portls="portmaster -L"
alias portupg="sudo portmaster -aDG"

Speaking of such things (particularly the usage of -l/-L, which
shouldn't need root privileges), did you get my PR and patch to allow
for five-digit UIDs?

HTH,
Jim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

portmaster and environ from pkg_install tools (was: i keep trying to move from portupgrade to portmaster)

2010-08-06 Thread Andres Perera

On Fri, Aug 6, 2010 at 5:41 PM, Doug Barton  wrote:
> On 08/06/2010 15:03, Adam Vande More wrote:
>
>> While your in the mood for for taking portmaster suggestions,
>
> I am always in the mood for taking suggestions. :)
>

On that note, I suggest that portmaster should fallback on PKG_PATH,
which is explained in pkg_add(1), if LOCAL_PACKAGEDIR isn't defined.

I'm setting it like this anyhow in portmaster.rc, but it makes sense as
a default. I was suprised that it didn't use this when I began using
portmaster.

Andres
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: portmaster and environ from pkg_install tools (was: i keep trying to move from portupgrade to portmaster)

On 08/06/2010 16:01, Andres Perera wrote:
> On Fri, Aug 6, 2010 at 5:41 PM, Doug Barton  wrote:
>> On 08/06/2010 15:03, Adam Vande More wrote:
>>
>>> While your in the mood for for taking portmaster suggestions,
>>
>> I am always in the mood for taking suggestions. :)
>>
> 
> On that note, I suggest that portmaster should fallback on PKG_PATH,
> which is explained in pkg_add(1), if LOCAL_PACKAGEDIR isn't defined.

It uses PACKAGES if LOCAL_PACKAGEDIR is not defined, which is a
throwback to the days before package installation support because it
uses that location for other things too.


Doug

-- 

Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/

Computers are useless. They can only give you answers.
-- Pablo Picasso

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread Michel Talon

Doug Barton wrote:

> On 08/06/2010 15:03, Adam Vande More wrote:
> 
> > While your in the mood for for taking portmaster suggestions,
> 
> I am always in the mood for taking suggestions. :)
> 
> > I think an
> > option to backup all currently installed packages would be useful. 
> 
> for pkg in /var/db/pkg/* ; do
>   pkg_create -b $pkg
> done
> 
> > I
> > have a python script that does this for me, but it would be easy
> > enough
> > to use sh as well.  I do this because there have been too many times
> > something has broken during a port upgrade run

I don't think pkg_create preserves the config files user edited, which
is the precious stuff, but it preserves a lot of useless stuff.
The following python script by Cyrille Szymanski may be more useful:
http://www.lpthe.jussieu.fr/~talon/pkg_save.py
It keeps the config files and the shared libraries.

-- 

Michel TALON

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

On Fri, Aug 6, 2010 at 5:11 PM, Doug Barton  wrote:

> On 08/06/2010 15:03, Adam Vande More wrote:
>
> for pkg in /var/db/pkg/* ; do
>pkg_create -b $pkg
> done
>

Yes, that is basically what I'm talking about, my script is a little fancier
now, prompts for directory with a default if you just want to use a standard
location.  Also can create directory or clean out an existing one.

> > have a python script that does this for me, but it would be easy enough
> > to use sh as well.  I do this because there have been too many times
> > something has broken during a port upgrade run and I need to revert
> > immediately and fix later.  I realize the backup package feature sort of
> > does the same thing, but reconciling the pre- and post- updates is a
> > tough thing for me.  Having a user defined directory all currently
> > installed ports can be put in is much easier to work with IMO. I know of
> > other people doing similar things because I shared my script on
> > questions- and got a few responses awhile ago.
>
> It sounds like you want to add the option(s) for "create and keep a
> backup package of an installed port" and/or "create a package of the new
> port" either to your command line, wrapper script, or a portmaster rc
> file. You could use the command line above to create an up to date
> repository of your currently installed packages, and the 2 options above
> would both make sure you can back out an update and keep your local
> package repo up to date automatically.
>

Yeah, I can and do this via a wrapper, it's certainly works well enough.
Maybe some triggers users could set to run pre- and post- postmaster runs?
But as you you say, easy enough to do with a wrapper.

I don't think pkg_create preserves the config files user edited, which
> is the precious stuff, but it preserves a lot of useless stuff.
> The following python script by Cyrille Szymanski may be more useful:
> http://www.lpthe.jussieu.fr/~talon/pkg_save.py
> It keeps the config files and the shared libraries.

Yes that's a great script for managing individual packages.  Mine is much
simpler and there is no need for backing up shared libs since your dealing
with a package "snapshot".  I also backup /usr/local/etc separately which is
where all the package config files I care about live.

Also

-- 
Adam Vande More
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Next question from a basically novice maintainer

OK, I'm trying to set up tinderbox to validate the port I maintain and
another that I'm attempting to put together (well, technically to
update since the maintainer has not responded to my inquiry).  How do
I set up ports trees for individual ports and their dependencies?  The
README only shows how to pull a full ports tree from CVS.

Thanks,
Jim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread jhell

On 08/06/2010 17:26, Doug Barton wrote:
>> and force creation of whatever you have on the system already?
> Not sure what this means, can you explain it in more detail?

No matter what the state of a package is I feel deeply that when making
a backup package, that should not fail because of a missing file that
might have been caused by a incorrect pkg-plist or whatever.

Most of the times I have noticed backup package creation fail was caused
by tar(1) or other tools not being able to stat a file or directory.

For instance:
Creating bzip'd tar ball in
'/exports/packages/GraphicsMagick-1.1.15_3,1.tbz'
tar: lib/ImageMagick-6.6.2/modules-Q16/coders/djvu.la: Cannot stat: No
such file or directory
tar: lib/ImageMagick-6.6.2/modules-Q16/coders/djvu.so: Cannot stat: No
such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256

And this has left the GraphicsMagick package incomplete. I would believe
that portmaster is probably dealing with the same problem.

> 
>> > Configuration option to email the output of upgraded packages and their
>> > pkg-message or a similar option to just log to a file?
> The ability to log actions to a file is already in the dev version in
> svn. You have to specify PM_LOG in your rc file. I want to see how that
> goes first before I consider adding a command line option for it. I
> don't anticipate adding e-mail functionality to portmaster, that sounds
> like something that should be done in a wrapper script, along with
> PM_LOG. (Although, there was a meme from the early days that no Unix app
> is complete until it grows the ability to do e-mail, so you never know ...)
> 

I agree with you on this. Seeing as PM_LOG will be there that makes it
much easier to deal with.

-- 

 jhell,v

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: i keep trying to move from portupgrade to portmaster

2010-08-06 Thread jhell

On 08/06/2010 18:03, Adam Vande More wrote:
> On Fri, Aug 6, 2010 at 4:26 PM, Doug Barton  wrote:
> 
>> I need to add an option for this, but it will likely be an "expert"
>> option that you can set in the rc file. The theory is that package
>> creation failure should be a rare thing, and since portmaster has no way
>> to know what packages are really critical to any given system it treats
>> inability to safely recover from an upgrade failure as a critical error.
>> However, having the ability to disable this is an oft-requested feature,
>> I just haven't gotten to it yet.
>>
>> I actually took a look at the code in this area last night with an eye
>> towards creating this option, I'll see if I can get it done for the next
>> release.
>>
> 
> While your in the mood for for taking portmaster suggestions, I think an
> option to backup all currently installed packages would be useful.  I have a
> python script that does this for me, but it would be easy enough to use sh
> as well.  I do this because there have been too many times something has
> broken during a port upgrade run and I need to revert immediately and fix
> later.  I realize the backup package feature sort of does the same thing,
> but reconciling the pre- and post- updates is a tough thing for me.  Having
> a user defined directory all currently installed ports can be put in is much
> easier to work with IMO. I know of other people doing similar things because
> I shared my script on questions- and got a few responses awhile ago.
> 

Just for reference. Doug B. has already touched on this.

#!/bin/sh

trap 'exit 1' 2

_pkg_bld(){
  cd /exports/packages
  for package in `ls /var/db/pkg |sed 's/pkgdb.db//'`; do
echo "Building package: $package"
pkg_create -v -b $package >>pkg_bld.log 2>&1
  done
}

_pkg_bld


I never did add a test to see if the package was already there but then
again I used this before extreme situations that the upgrades would span
the whole ports tree.

-- 

 jhell,v

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD unmaintained ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments. The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm. Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below. In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type. (By 'build environment' here we
mean 'combination of 6.x/7.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version. The program
that generates this report is not yet able to determine this
automatically.)

portname: audio/audacious-crossfade
broken because: Does not compile
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=audacious-crossfade

portname: audio/ecamegapedal
broken because: does not compile
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecamegapedal

portname: audio/lmms
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=lmms

portname: audio/terminatorx
broken because: does not compile
build errors:
http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20100704113633/terminatorx-3.82_12.log.bz2
(_Jul_14_02:48:48_UTC_2010)
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=terminatorx

portname: chinese/chinput3
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=chinput3

portname: comms/asmodem
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=asmodem

portname: comms/ltmdm
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=ltmdm

portname: comms/yawmppp
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=yawmppp

portname: databases/p5-sqlrelay
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=p5-sqlrelay

portname: devel/ace+tao
broken because: Does not compile on FreeBSD >= 7.0
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ace%2Btao

portname: devel/fampp
broken because: FAM system mismatch: gamin is installed, while desired
FAM system is fam
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp

portname: devel/gcvs
broken because: does not compile
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gcvs

portname: devel/linux-js
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-js

portname: devel/linuxthreads
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linuxthreads

portname: devel/ngpt
broken because: does not compile
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ngpt

portname: devel/p5-ORBit
broken because: Does not compile with GCC 4.2
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-OR

FreeBSD ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 6.x/7.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   audio/audacious-crossfade
broken because: Does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=audacious-crossfade


portname:   audio/aureal-kmod
broken because: doesn't build on RELENG_8
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=aureal-kmod


portname:   audio/baudline
broken because: no longer available (website now have 1.08)
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.6.20100803081833/linux-baudline-1.07.log
 (_Jul_30_10:57:11_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=baudline


portname:   audio/ecamegapedal
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecamegapedal


portname:   audio/ecawave
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ecawave


portname:   audio/emu10kx
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=emu10kx


portname:   audio/gmpc-mserver
broken because: fails to build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gmpc-mserver


portname:   audio/lmms
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=lmms


portname:   audio/muse
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=muse


portname:   audio/terminatorx
broken because: does not compile
build errors:
http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20100704113633/terminatorx-3.82_12.log.bz2
 (_Jul_14_02:48:48_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=terminatorx


portname:   benchmarks/polygraph
broken because: does not build
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20100319084642/polygraph-3.0.6_1.log
 (_Mar_21_01:42:24_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph


portname:   benchmarks/polygraph31
broken because: does not build
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20100319084642/polygraph31-3.1.5_1.log
 (_Mar_21_01:42:25_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph31


portname:   cad/alliance
broken because: incomplete plist
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=alliance


portname:   cad/tclspice
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=tclspice


portname:   chinese/chinput3
broken because: does not build
build erro

FreeBSD ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   archivers/py-tarfile
description:Python library for reading and writing tarballs
maintainer: po...@freebsd.org
deprecated because: all development activity in this port has been merged
into mainline python after 2.4
expiration date:2010-08-07
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=py-tarfile


portname:   databases/sqlite-ext-inet
description:Library will provide the ipv4 functions in SQL queries
maintainer: p...@iib.ru
deprecated because: Please install databases/sqlite-ext-mobigroup instead
expiration date:2010-09-05
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=sqlite-ext-inet


portname:   deskutils/linux-sunbird
description:Calendaring application branched from Mozilla
maintainer: ge...@freebsd.org
deprecated because: Upstream development discontinued. Please consider
using /home/linimon/ports/deskutils/lightning instead
expiration date:2010-09-04
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=linux-sunbird


portname:   deskutils/sunbird
description:Redesign of the Mozilla Calendar with XUL interface
maintainer: ge...@freebsd.org
deprecated because: Upstream development discontinued. Please consider
using /home/linimon/ports/deskutils/lightning instead
expiration date:2010-09-04
build errors:
http://pointyhat.freebsd.org/errorlogs/ia64-errorlogs/e.8.20100305224420/sunbird-0.9_2,1.log.bz2
 (_Mar_29_05:07:56_UTC_2010)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=sunbird


portname:   deskutils/sunbird-i18n
description:Localized interface for Sunbird
maintainer: ge...@freebsd.org
deprecated because: Upstream development discontinued. Please consider
using /home/linimon/ports/deskutils/lightning instead
expiration date:2010-09-04
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=sunbird-i18n


portname:   devel/codeville
description:An "anarchic" control version system without
unnecessary re-merges
maintainer: po...@freebsd.org
deprecated because: Dead project.
expiration date:2010-08-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=codeville


portname:   devel/p5-P4-Client
description:P4::Client - Perl extension for the Perforce API
maintainer: to...@freebsd.org
status: BROKEN
deprecated because: has been broken for 11 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=p5-P4-Client


portname:   editors/koffice-kde4-l10n-fy
description:Frisian messages and documentation for KOffice2
maintainer: k...@freebsd.org
status: IGNORE
deprecated because: 
expiration date:2010-08-07
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=koffice-kde4-l10n-fy


portname:   editors/koffice-kde4-l10n-hne
description:Chhattisgarhi messages and documentation for KOffice2
maintainer: k...@freebsd.org
status: IGNORE
deprecated because: 
expiration date:2010-08-07
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=koffice-kde4-l10n-hne


portname:   editors/koffice-kde4-l10n-wa
description:Walloon Bokmaal messages and documentation for
KOffice2
maintainer: k...@freebsd.org
status: IGNORE
deprecated because: 
expiration date:2010-08-07
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=editors&portname=koffice-kde4-l10n-wa


portname:   graphics/lphoto
description:A complete desktop solution for digita

FreeBSD unmaintained ports which are currently marked forbidden

As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles.  Often,
these ports are so marked due to security concerns, such as known
exploits.

An overview of each port, including errors seen on the build farm,
is included below.

portname:   misc/compat3x
forbidden because:  FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath  - not
fixed / no lib available
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD unmaintained ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   archivers/py-tarfile
description:Python library for reading and writing tarballs
maintainer: po...@freebsd.org
deprecated because: all development activity in this port has been merged
into mainline python after 2.4
expiration date:2010-08-07
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=py-tarfile


portname:   devel/codeville
description:An "anarchic" control version system without
unnecessary re-merges
maintainer: po...@freebsd.org
deprecated because: Dead project.
expiration date:2010-08-31
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=codeville


portname:   graphics/lphoto
description:A complete desktop solution for digital photo
management
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: broken
expiration date:2010-03-30
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=lphoto


portname:   mail/ngmp
description:A full AJAX based web app for messaging and
collaboration
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: does not compile and no longer supported by upstream
expiration date:2010-08-18
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=ngmp


portname:   net-mgmt/net-snmp4
description:An extendable SNMP implementation
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: Use net-mgmt/net-snmp port instead
expiration date:2009-07-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=net-snmp4


portname:   net-p2p/javadc
description:Open source Java DirectConnect (TM) command-line
client
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: is ancient, unmaintained, works only with JDK 1.3, no
master site
expiration date:2010-08-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=javadc


portname:   net/pathchar
description:LBNL Internet path characterization tool
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: has been broken for 2+ years, no sources available
expiration date:2010-09-01
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=pathchar


portname:   textproc/py-xmltools
description:High level XML tools for Python
maintainer: po...@freebsd.org
status: BROKEN
deprecated because: has been broken for 4 months
expiration date:2010-01-08
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=py-xmltools


portname:   www/linux-nvu
description:A complete Web Authoring System
maintainer: po...@freebsd.org
deprecated because: NVU 1.0, released June 2005, is the last official
release of NVU.  Kompozer has picked up where NVU has
left off. Please consider using 
/home/linimon/ports/www/kompozer instead
expiration date:2010-08-05
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-nvu
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports which are currently marked forbidden