Fw: Re: FreeBSD ports which are currently scheduled for deletion

Jeffrey Bouquet jeffreybouquet at yahoo.com
Wed Apr 16 20:01:12 UTC 2014


Third attempt to send to the list ( a forwarding of a saved SENT message.)
However another question
In the make.conf there is WITH_NEW_XORG
but I've not the vt(9) driver.

UPDATING is not clear (today 4 16) enough as to wheter WITH_NEW_XORG 
should remain, or be replaced with WITHOUT before updating DRI since I've not
a 9-STABLE rebuilt since its introduction probably.

Questions below remain.
Apologizing for top posting, but the bottom posting does not appear at the list yet.
Glitch somewhere.

Don't know if the email arriving is more important than the questions in the 
email or not...

--- On Tue, 4/15/14, Jeffrey Bouquet <jeffreybouquet at yahoo.com> wrote:

> From: Jeffrey Bouquet <jeffreybouquet at yahoo.com>
> Subject: Re: FreeBSD ports which are currently scheduled for deletion
> To: "ports list" <freebsd-ports at freebsd.org>
> Date: Tuesday, April 15, 2014, 6:16 PM
> --------------------------------------------
> On Sun, 4/13/14, Jeffrey Bouquet <jeffreybouquet at yahoo.com>
> wrote:
> 
>  Subject: Re: FreeBSD ports which are currently scheduled
> for deletion
>  To: freebsd-ports at freebsd.org
>  Date: Sunday, April 13, 2014, 11:45 AM
>  
>   
>   On 4/13/2014 17:46, Matthew Rezny
>   wrote:
>  
>   >>> On this list I see cfv, which I've used for
>   years, marked just because
>   >>> it's
>   >>> not maintained. It works great, it needs no
>   changes. 
>  
>  
>   > I'm not officially a maintainer on any ports for a
>  few
>   reasons. I have other 
>   > areas where I consider spending my time more
>  valuable,
>   but if I have to waste 
>   > it on port maintenance, I'll try to do so in the
> most
>   efficient way. 
>   
>   Well, you basically said you're more important than
>  anybody
>   that
>   regularly reads this list, so good luck with that tact.
>  
> .......................................................................................I
>  regularly
>  ........................................................................................read
>  this list
>  .........................................................................................and
>  also
>  ......................................................................................have
>  not the
>  ...................................................................................experience
>  or time
>   So you should become a committer.
>    
>   Try submitting the patches, including staging and
> assuming
>   maintainership (and then honestly be the maintainer). 
>   
>    Staging is not an opt-in feature so as
>   harsh as it is to
>   say
>   
>   This indicates that you haven't been paying attention. 
>   
>   It's not a goal to have the most
>   ports possible; 
>   
>  ...............................................Maybe take
>  changes to a 
>  subsection of the forum? I've posted there...
>  
>  A new subsection group: ports
>  X11...
>  WWW...
>  DEVEL...
>  maybe one DELETIONS ( a sticky or subsection)
>  and/or PENDING DELETIONS ... and/or
>  and deleted ports could be bought back again for those
>  who find them useful, even if someone was reading about
>  a years-ago removal.
>  
>  Pardiff (diffp ) comes to mind (just removed this week)
>  I use the diffp binary for diffing ports-to-upgrade pipe
>  results between days (diffp portlist.MON portlist.TUE)
>  I suppose mergemaster.sh could even be updated to
>  be more similar to the output of diffp.
>  .....
>  gfontview... 
>  ...
>  
>  Just puttting that idea onto the forum expansion, which
>  maybe could solve problems quicker than PR's.
>  For instance, as of now,
>  textproc/po4a
>  x11/roxterm
>  devel/dconf
>  
>  all fail to build "failed to load exteral entity "http://docbook.sourceforge.net/release/
>  xsl/current/manpages/docbook.xsl"  "
>  
>  and maybe if the forum had been expanded, threads (dconf
>  po4a roxterm) would
>  have been started/updated explaining the fix, if anyone
> knew
>  it. 
>  
> 
> ...............................................
> Lost post en route to the list [ addressee maybe
> incomplete]   Re-sending from the SENT
> folder. 
> Sorry for the delay...
> 


More information about the freebsd-ports mailing list