Re: Dropping maintainership of my Ports

[Adam Weinberger]

On Sat, Mar 28, 2020 at 1:01 PM Peter Pentchev  wrote:
>
> On Sat, Mar 28, 2020 at 07:25:32PM +0100, Mateusz Piotrowski wrote:
> > On 3/28/20 5:33 PM, Peter Pentchev wrote:
> > > On Fri, Mar 27, 2020 at 05:35:44PM -0700, Neel Chauhan wrote:
> > > > Hi freebsd-ports@,
> > > >
> > > > I would like to drop maintainership for the following Ports:
> > Thanks, Neel!
> > > [snip]
> > > > net/librsync2
> > > > sysutils/ioping
> > > > sysutils/pick
> > > Hi,
> > >
> > > If no one has already stepped up, I'd like to try my hand at maintaining
> > > these three as a way of tentatively slowly coming back to FreeBSD.
> >
> > Sure! Could you submit appropriate patches to bugzilla?
>
> Bah, nevermind, people beat me to it for all three :) No worries :)
>
> G'luck,
> Peter

librsync2 and ioping were claimed a couple hours before you requested
those ports, but pick was claimed about 90 minutes after.

It's tobik@'s call as he took maintainership, but you did request it.
Regardless of whether Tobias wants to retain maintainership, please
take a look at https://portscout.freebsd.org/po...@freebsd.org.html
and see if there are some other ports you'd be interested in
maintaining. We'd love to lure you back to FreeBSD ports.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Dropping maintainership of my Ports

[Peter Pentchev]

On Sat, Mar 28, 2020 at 07:25:32PM +0100, Mateusz Piotrowski wrote:
> On 3/28/20 5:33 PM, Peter Pentchev wrote:
> > On Fri, Mar 27, 2020 at 05:35:44PM -0700, Neel Chauhan wrote:
> > > Hi freebsd-ports@,
> > > 
> > > I would like to drop maintainership for the following Ports:
> Thanks, Neel!
> > [snip]
> > > net/librsync2
> > > sysutils/ioping
> > > sysutils/pick
> > Hi,
> > 
> > If no one has already stepped up, I'd like to try my hand at maintaining
> > these three as a way of tentatively slowly coming back to FreeBSD.
> 
> Sure! Could you submit appropriate patches to bugzilla?

Bah, nevermind, people beat me to it for all three :) No worries :)

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Re: Dropping maintainership of my Ports

[Mateusz Piotrowski]

On 3/28/20 5:33 PM, Peter Pentchev wrote:

On Fri, Mar 27, 2020 at 05:35:44PM -0700, Neel Chauhan wrote:

Hi freebsd-ports@,

I would like to drop maintainership for the following Ports:

Thanks, Neel!

[snip]

net/librsync2
sysutils/ioping
sysutils/pick

Hi,

If no one has already stepped up, I'd like to try my hand at maintaining
these three as a way of tentatively slowly coming back to FreeBSD.


Sure! Could you submit appropriate patches to bugzilla?

Thanks!

Mateusz

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

Re: Dropping maintainership of my Ports

[Peter Pentchev]

On Fri, Mar 27, 2020 at 05:35:44PM -0700, Neel Chauhan wrote:
> Hi freebsd-ports@,
> 
> I would like to drop maintainership for the following Ports:
> 
[snip]
> net/librsync2
> sysutils/ioping
> sysutils/pick

Hi,

If no one has already stepped up, I'd like to try my hand at maintaining
these three as a way of tentatively slowly coming back to FreeBSD.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Re: Dropping maintainership of my Ports

[Russell Haley]

Thanks for all your hard work Neel!

On Friday, March 27, 2020, Neel Chauhan  wrote:

> Hi freebsd-ports@,
>
> I would like to drop maintainership for the following Ports:
>
> databases/py-mysqlclient
> deskutils/go-for-it
> devel/grpc
> devel/libnsutils
> devel/libparserutils
> devel/netsurf-buildsystem
> devel/nsgenbind
> dns/libnspsl
> emulators/nestopia
> graphics/cloudcompare
> graphics/glfw
> graphics/libnsbmp
> graphics/libnsgif
> graphics/maim
> graphics/py-glfw
> math/py-keras
> multimedia/gtk-youtube-viewer
> net/librsync2
> net/yaz
> security/i2p
> sysutils/ioping
> sysutils/pick
> sysutils/ttyd
> sysutils/zrep
> textproc/libcss
> textproc/libwapcaplet
> www/itop
> www/libdom
> www/libhubhub
> www/mohawk
> www/mongrel2
> www/netsurf
> x11/slop
>
> I am no longer interested in maintaining Ports, after many months of
> half-hearted work if not neglect. I still plan to contribute to FreeBSD,
> just that my focus is now on the TCP/IP networking stack.
>
> Could someone please reset the maintainership of the ports above?
>
> -Neel
>
> ===
>
> https://www.neelc.org/
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Dropping maintainership of my Ports

[Rene Ladan]

On Fri, Mar 27, 2020 at 05:35:44PM -0700, Neel Chauhan wrote:
> Hi freebsd-ports@,
> 
> I would like to drop maintainership for the following Ports:
> 
> databases/py-mysqlclient
> deskutils/go-for-it
> devel/grpc
> devel/libnsutils
> devel/libparserutils
> devel/netsurf-buildsystem
> devel/nsgenbind
> dns/libnspsl
> emulators/nestopia
> graphics/cloudcompare
> graphics/glfw
> graphics/libnsbmp
> graphics/libnsgif
> graphics/maim
> graphics/py-glfw
> math/py-keras
> multimedia/gtk-youtube-viewer
> net/librsync2
> net/yaz
> security/i2p
> sysutils/ioping
> sysutils/pick
> sysutils/ttyd
> sysutils/zrep
> textproc/libcss
> textproc/libwapcaplet
> www/itop
> www/libdom
> www/libhubhub
> www/mohawk
> www/mongrel2
> www/netsurf
> x11/slop
> 
> I am no longer interested in maintaining Ports, after many months of
> half-hearted work if not neglect. I still plan to contribute to FreeBSD,
> just that my focus is now on the TCP/IP networking stack.
> 
> Could someone please reset the maintainership of the ports above?
> 
Done, thanks for your past contributions.

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

Dropping maintainership of my Ports

[Neel Chauhan]

Hi freebsd-ports@,

I would like to drop maintainership for the following Ports:

databases/py-mysqlclient
deskutils/go-for-it
devel/grpc
devel/libnsutils
devel/libparserutils
devel/netsurf-buildsystem
devel/nsgenbind
dns/libnspsl
emulators/nestopia
graphics/cloudcompare
graphics/glfw
graphics/libnsbmp
graphics/libnsgif
graphics/maim
graphics/py-glfw
math/py-keras
multimedia/gtk-youtube-viewer
net/librsync2
net/yaz
security/i2p
sysutils/ioping
sysutils/pick
sysutils/ttyd
sysutils/zrep
textproc/libcss
textproc/libwapcaplet
www/itop
www/libdom
www/libhubhub
www/mohawk
www/mongrel2
www/netsurf
x11/slop

I am no longer interested in maintaining Ports, after many months of 
half-hearted work if not neglect. I still plan to contribute to FreeBSD, 
just that my focus is now on the TCP/IP networking stack.


Could someone please reset the maintainership of the ports above?

-Neel

===

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

Re: Will 10.3 clobber my ports area?

[Dave Horsfall]

On Tue, 4 Oct 2016, Kevin Oberman wrote:

[ Reloading ports ]

> Of course. You can use portsnap(8) to do this. See 4.5 - Using the Ports 
> Collection 
>  
> for details. It's quite trivial. This also will give you the latest 
> versions of all ports.

Many thanks!  Now to pick a time to gird my loins...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Will 10.3 clobber my ports area?

[Kevin Oberman]

On Tue, Oct 4, 2016 at 8:04 PM, Dave Horsfall  wrote:

> On Mon, 3 Oct 2016, Kevin Oberman wrote:
>
> > The ports will not be touched, but some will not run on 10.3 because of
> > ABI changes in some shareable libraries. Most of the base system uses
> > versioned symbols, so will work fine, but some, usually contributed
> > code, don't. Ports that use them will need to be re-installed/rebuilt.
>
> [...]
>
> Many thanks; I'm a bit nervous, as this is my only FreeBSD server :-)
>
> I know I'm going to have trouble with the ports area anyway, because I
> seem to have corrupted it somehow (during the switch between pkg* etc),
> and I cannot seem to reload it from the CD (disc1).  Is there a way to
> fetch the entire ports tree online?
>
> Oh, this is for Joseph Mingrove: my mail log shows a message from you
> (relayed via FreeBSD.org) but there's nothing in my mailbox about it (and
> it certainly wasn't rejected).  I guess I accidentally deleted it, so
> could you please send it again?
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
>

Of course. You can use portsnap(8) to do this. See 4.5 - Using the Ports
Collection

for details. It's quite trivial. This also will give you the latest
versions of all ports.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Will 10.3 clobber my ports area?

[Dave Horsfall]

On Wed, 5 Oct 2016, Dave Horsfall wrote:

> Oh, this is for Joseph Mingrove: my mail log shows a message from you 
> (relayed via FreeBSD.org) but there's nothing in my mailbox about it 
> (and it certainly wasn't rejected).  I guess I accidentally deleted it, 
> so could you please send it again?

Skip it; it would've been some unassociated message on the list...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Will 10.3 clobber my ports area?

[Dave Horsfall]

On Mon, 3 Oct 2016, Kevin Oberman wrote:

> The ports will not be touched, but some will not run on 10.3 because of 
> ABI changes in some shareable libraries. Most of the base system uses 
> versioned symbols, so will work fine, but some, usually contributed 
> code, don't. Ports that use them will need to be re-installed/rebuilt.

[...]

Many thanks; I'm a bit nervous, as this is my only FreeBSD server :-)

I know I'm going to have trouble with the ports area anyway, because I 
seem to have corrupted it somehow (during the switch between pkg* etc), 
and I cannot seem to reload it from the CD (disc1).  Is there a way to 
fetch the entire ports tree online?

Oh, this is for Joseph Mingrove: my mail log shows a message from you 
(relayed via FreeBSD.org) but there's nothing in my mailbox about it (and 
it certainly wasn't rejected).  I guess I accidentally deleted it, so 
could you please send it again?

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Will 10.3 clobber my ports area?

[Kevin Oberman]

On Mon, Oct 3, 2016 at 7:29 PM, Dave Horsfall  wrote:

> Assuming the binary upgrade from 9.3 to 10.3 is "clean" i.e. it won't
> clobber any of my local stuff (this is my only FreeBSD server), what will
> happen to the ports area?  Left alone, saved, or overwritten with/without
> any local chnages?
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
>

The ports will not be touched, but some will not run on 10.3 because of ABI
changes in some shareable libraries. Most of the base system uses versioned
symbols, so will work fine, but some, usually contributed code, don't.
Ports that use them will need to be re-installed/rebuilt.

It is recommended that, when moving between major versions, all ports be
re-installed, but most won't need it. The tricky part is finding those that
need rebuilding. While mixing ports and packages is nto generally
recommended, I would upgrade all ports that have default configurations be
re-installed from packages. Those that have custom configurations will, of
course need to be re-built.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Will 10.3 clobber my ports area?

[Dave Horsfall]

Assuming the binary upgrade from 9.3 to 10.3 is "clean" i.e. it won't 
clobber any of my local stuff (this is my only FreeBSD server), what will 
happen to the ports area?  Left alone, saved, or overwritten with/without 
any local chnages?

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Rebuilding my ports area

[Dave Horsfall]

FreeBSD 9.3-RELEASE-p20 (GENERIC) #0: Tue Jul 21 19:29:33 UTC 2015

Having completely scragged my ports area following various changes to 
pkg/pkgng/etc, and being unable to sysinstall it from CD (not found for 
some reason) or via FTP (not found on server etc), I found a pristine copy 
of ports.txz and unpacked it (sigh, yet another compression scheme), after 
renaming the old directory.

Anyway, what do I do now?  Assume that many ports have been installed, and 
that the databases etc are probably a dog's breakfast, per the conflicts 
that I have posted here earlier.  If it helps, I have a list of those 
ports that were installed, and hopefully the dependencies will be taken 
care of automagically.

Thanks.

-- 
Dave Horsfall DTM (VK2KFU)  Those who don't understand security will suffer
Watson never said I think there is a world market for maybe five computers.
___
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: Rebuilding my ports area

[Chris H]

On Fri, 24 Jul 2015 17:21:07 +1000 (EST) Dave Horsfall d...@horsfall.org
wrote

 FreeBSD 9.3-RELEASE-p20 (GENERIC) #0: Tue Jul 21 19:29:33 UTC 2015
 
 Having completely scragged my ports area following various changes to 
 pkg/pkgng/etc, and being unable to sysinstall it from CD (not found for 
 some reason) or via FTP (not found on server etc), I found a pristine copy 
 of ports.txz and unpacked it (sigh, yet another compression scheme), after 
 renaming the old directory.
 
 Anyway, what do I do now?  Assume that many ports have been installed, and 
 that the databases etc are probably a dog's breakfast, per the conflicts 
 that I have posted here earlier.  If it helps, I have a list of those 
 ports that were installed, and hopefully the dependencies will be taken 
 care of automagically.
 
 Thanks.
Maybe I'm missing something regarding your particular situation. But
wouldn't
svn co svn://svn.freebsd.org/ports/head /usr/ports
have given it to you?

--Chris
 
 -- 
 Dave Horsfall DTM (VK2KFU)  Those who don't understand security will suffer
 Watson never said I think there is a world market for maybe five computers.
 ___
 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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Rebuilding my ports area

[David Wolfskill]

On Fri, Jul 24, 2015 at 05:21:07PM +1000, Dave Horsfall wrote:
 FreeBSD 9.3-RELEASE-p20 (GENERIC) #0: Tue Jul 21 19:29:33 UTC 2015
 
 Having completely scragged my ports area following various changes to 
 pkg/pkgng/etc, and being unable to sysinstall it from CD (not found for 
 some reason) or via FTP (not found on server etc), I found a pristine copy 
 of ports.txz and unpacked it (sigh, yet another compression scheme), after 
 renaming the old directory.
 
 Anyway, what do I do now?  Assume that many ports have been installed, and 
 that the databases etc are probably a dog's breakfast, per the conflicts 
 that I have posted here earlier.  If it helps, I have a list of those 
 ports that were installed, and hopefully the dependencies will be taken 
 care of automagically.
 

Near the bottom of portmaster(8), there is a procedure entitled Using
portmaster to do a complete reinstallation of all your ports.  I have
used that procedure (with some variations) over the years -- e.g.,
migrating from 8.x - 9.x, then 9.x to  10.x; more recently, I extracted
bits of it to migrate from stable/10 i386 - stable/10 amd64 [gory
details at
http://www.catwhisker.org/~david/FreeBSD/convert_i386_amd64.html].

Based on my experiences doing those, I *think* that using that procedure
as a basis (and adapting in slightly) may serve you well.  (Note that as
of this writing, that procedure still refers to the old pkg_* tools.  So
instead of pkg_delete -a I used pkg delete -fa.)

One of the first things, though, would be to determine if you'r going to
use pre-built packages (and if so, built by whom) or build the ports
yourself.

The procedure I used in the above-cited article -- once I finished
bumping into issues caused by my ignorance (or other oddities) -- turned
out to work quite well -- but I was only able to accomplish it because I
had available hardware to perform the package-building (using poudriere)
for me.

portmaster itself is merely a shell script, so it has no dependencies
on (other) ports; installing it on a pristine system will bring in pkg,
but no others.

Note, too: after generating the list of 'installed ports (which may
look incomplete: it doesn't actually list all of your inistalled ports,
but rather, a subset that is necessary to get all of them installed), I
finid it useful to trim the list further and re-order the list (so that
more critical, smaller port -- such as sudo and tmux -- are built before
more complicated ports cause problems).  One of the things I typically
do on non-development machines during this pass is remove ports from the
list that are obviously only build dependencies -- autoconf*;
automake*; nearly all devel/* ports -- as the installation of the ports
I really use directly will bring the others in if they are actually needed.

If at all possible, of course, make a good (tested!) backup before you
do the pkg delete -af. :-}

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Those who murder in the name of God or prophet are blasphemous cowards.

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


pgpGvjRCcGXnw.pgp
Description: PGP signature

Re: Rebuilding my ports area

[Warren Block]

On Fri, 24 Jul 2015, David Wolfskill wrote:


On Fri, Jul 24, 2015 at 05:21:07PM +1000, Dave Horsfall wrote:

FreeBSD 9.3-RELEASE-p20 (GENERIC) #0: Tue Jul 21 19:29:33 UTC 2015

Having completely scragged my ports area following various changes to
pkg/pkgng/etc, and being unable to sysinstall it from CD (not found for
some reason) or via FTP (not found on server etc), I found a pristine copy
of ports.txz and unpacked it (sigh, yet another compression scheme), after
renaming the old directory.

Anyway, what do I do now?  Assume that many ports have been installed, and
that the databases etc are probably a dog's breakfast, per the conflicts
that I have posted here earlier.  If it helps, I have a list of those
ports that were installed, and hopefully the dependencies will be taken
care of automagically.



Near the bottom of portmaster(8), there is a procedure entitled Using
portmaster to do a complete reinstallation of all your ports.  I have
used that procedure (with some variations) over the years -- e.g.,
migrating from 8.x - 9.x, then 9.x to  10.x; more recently, I extracted
bits of it to migrate from stable/10 i386 - stable/10 amd64 [gory
details at
http://www.catwhisker.org/~david/FreeBSD/convert_i386_amd64.html].


Updated portmaster man page procedure here:
https://forums.freebsd.org/threads/rebuilding-all-ports-with-portmaster.51210/
___
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

Getting rid of my ports

[Paul Schmehl]

I am retiring at the end of January.  I will no longer be able to maintain 
ports (nor will I have much interest in doing so), so I need volunteers to 
take them over.  They should all be up to date (although I haven't checked 
today.)


Here's the list:

# make search key=pa...@utdallas.edu | grep Port
Port:   byaccj-1.15
Port:   liblognorm-1.0.0_1
Port:   p5-Iodef-Pb-Simple-0.21
Port:   p5-Net-DNS-Match-0.05
Port:   p5-Parse-Range-0.96
Port:   p5-IP-Anonymous-0.04
Port:   p5-Net-Nessus-XMLRPC-0.30_1
Port:   argus-sasl-3.0.8
Port:   argus-clients-sasl-3.0.8
Port:   p5-Net-Abuse-Utils-Spamhaus-0.04
Port:   afterglow-1.6.2
Port:   barnyard2-1.13
Port:   barnyard2-sguil-1.13
Port:   chaosreader-0.94_1
Port:   p5-Snort-Rule-1.07
Port:   sancp-1.6.1_5
Port:   spybye-0.3_4
Port:   p5-Linux-Cpuinfo-1.8
Port:   p5-CIF-Client-0.21
Port:   p5-REST-Client-249
Port:   iwidgets-4.0.1_1
Port:   p5-Gtk2-Ex-Dialogs-0.11_5
Port:   p5-Gtk2-Ex-Utils-0.09_6
Port:   p5-Gtk2-GladeXML-1.007_3

--
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
***
It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead. Thomas Jefferson
There are some ideas so wrong that only a very
intelligent person could believe in them. George Orwell

___
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: Getting rid of my ports

[Muhammad Moinur Rahman]

Hi,

I would like to volunteer.

BR,
Muhammad

On Wed, Nov 19, 2014 at 4:06 AM, Paul Schmehl pschmehl_li...@tx.rr.com
wrote:

 I am retiring at the end of January.  I will no longer be able to maintain
 ports (nor will I have much interest in doing so), so I need volunteers to
 take them over.  They should all be up to date (although I haven't checked
 today.)

 Here's the list:

 # make search key=pa...@utdallas.edu | grep Port
 Port:   byaccj-1.15
 Port:   liblognorm-1.0.0_1
 Port:   p5-Iodef-Pb-Simple-0.21
 Port:   p5-Net-DNS-Match-0.05
 Port:   p5-Parse-Range-0.96
 Port:   p5-IP-Anonymous-0.04
 Port:   p5-Net-Nessus-XMLRPC-0.30_1
 Port:   argus-sasl-3.0.8
 Port:   argus-clients-sasl-3.0.8
 Port:   p5-Net-Abuse-Utils-Spamhaus-0.04
 Port:   afterglow-1.6.2
 Port:   barnyard2-1.13
 Port:   barnyard2-sguil-1.13
 Port:   chaosreader-0.94_1
 Port:   p5-Snort-Rule-1.07
 Port:   sancp-1.6.1_5
 Port:   spybye-0.3_4
 Port:   p5-Linux-Cpuinfo-1.8
 Port:   p5-CIF-Client-0.21
 Port:   p5-REST-Client-249
 Port:   iwidgets-4.0.1_1
 Port:   p5-Gtk2-Ex-Dialogs-0.11_5
 Port:   p5-Gtk2-Ex-Utils-0.09_6
 Port:   p5-Gtk2-GladeXML-1.007_3

 --
 Paul Schmehl, Senior Infosec Analyst
 As if it wasn't already obvious, my opinions
 are my own and not those of my employer.
 ***
 It is as useless to argue with those who have
 renounced the use of reason as to administer
 medication to the dead. Thomas Jefferson
 There are some ideas so wrong that only a very
 intelligent person could believe in them. George Orwell

 ___
 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@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Getting rid of my ports

[A.J. 'Fonz' van Werven]

Paul Schmehl wrote:

 I will no longer be able to maintain ports
[snip]
 so I need volunteers to take them over.
[snip]
 Port: byaccj-1.15
 Port: chaosreader-0.94_1

I'd be happy to adopt the above two.

Regards,

AvW

-- 
Imbibo, ergo sum.


pgpT3Z5CEgyKN.pgp
Description: PGP signature

Re: Getting rid of my ports

[Kurt Jaeger]

Hi!

  Port:   byaccj-1.15
  Port:   chaosreader-0.94_1
 
 I'd be happy to adopt the above two.

You have those two.

-- 
p...@opsec.eu+49 171 3101372 6 years to go !
___
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: Getting rid of my ports

[A.J. 'Fonz' van Werven]

Kurt Jaeger wrote:

 Port:   byaccj-1.15
 Port:   chaosreader-0.94_1
 
 I'd be happy to adopt the above two.
 
 You have those two.

Thanks. I can submit PRs tomorrow (new maintainer address, additional
distfile mirror, etc.) if you want.

AvW

-- 
Imbibo, ergo sum.


pgpRtqAHl9U82.pgp
Description: PGP signature

Re: Getting rid of my ports

[Philippe Audéoud]

On Tue, 18 Nov 2014, Paul Schmehl wrote:

 I am retiring at the end of January.  I will no longer be able to maintain 
 ports (nor will I have much interest in doing so), so I need volunteers to 
 take them over.  They should all be up to date (although I haven't checked 
 today.)
 
 Here's the list:
 
 # make search key=pa...@utdallas.edu | grep Port
 Port: byaccj-1.15
 Port: liblognorm-1.0.0_1
 Port: p5-Iodef-Pb-Simple-0.21
 Port: p5-Net-DNS-Match-0.05
 Port: p5-Parse-Range-0.96
 Port: p5-IP-Anonymous-0.04
 Port: p5-Net-Nessus-XMLRPC-0.30_1
 Port: argus-sasl-3.0.8
 Port: argus-clients-sasl-3.0.8
 Port: p5-Net-Abuse-Utils-Spamhaus-0.04
 Port: afterglow-1.6.2
 Port: barnyard2-1.13
 Port: barnyard2-sguil-1.13
 Port: chaosreader-0.94_1
 Port: p5-Snort-Rule-1.07
 Port: sancp-1.6.1_5
 Port: spybye-0.3_4
 Port: p5-Linux-Cpuinfo-1.8
 Port: p5-CIF-Client-0.21
 Port: p5-REST-Client-249
 Port: iwidgets-4.0.1_1
 Port: p5-Gtk2-Ex-Dialogs-0.11_5
 Port: p5-Gtk2-Ex-Utils-0.09_6
 Port: p5-Gtk2-GladeXML-1.007_3


Hello,

If nobody for p5-*, you can set p...@freebsd.org as maintainer. We will
take care of them.

Regards,

-- 
Philippe Audéoud 
___
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: Keeping my ports tree in sync with the public pkg repo

[Darren Pilgrim]

On 6/12/2014 6:42 AM, Baptiste Daroussin wrote:

On Thu, Jun 12, 2014 at 06:11:13AM -0700, Darren Pilgrim wrote:

Is there a way to determine the ports tree revision used for the current
public pkg repo?



Right now you have no way but knowing that we take a snapshot of the ports tree
at 1am UTC every wednesday and build on it


I'll cron the svn update to coincide. That should make the race window 
narrow enough to be mostly avoided.



With pkg 1.3 we will add some metadata to the repo specifying the revision used
We also to plan to add a ports package so pkg install ports will install the
ports tree used to build the packages


Oh nice!  Exposing the revision number would be a really useful bit of 
info.  I could easily grab that and feed it to svn.

___
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

Keeping my ports tree in sync with the public pkg repo

[Darren Pilgrim]

Is there a way to determine the ports tree revision used for the current 
public pkg repo?


Like any moderately complex system, I have a mix of stock and custom 
packages.  When I go to update stuff, I'll check out the current ports 
tree and fire off poudrerie to build what I need.  There's a race 
condition: if more than a day or two elapse between when the public pkg 
repo was last refreshed and when I check out the ports tree, there's a 
good chance the version in ports and version of the available package 
don't match.  This is particularly true right now because of all the 
movement from staging and other recent framework changes.


The result is portmaster gives me hell.  I'll go to rebuild, say, perl 
or php using portmaster and it will tell me something I've installed 
from pkgs needs to be updated.  I then go check pkg update and it says 
it's up to date.


There are workarounds, but pkg lock shell games are fragile and I really 
dislike having stock builds of libxml, numerous build tools, vim-lite, 
etc. in my private repos.  If I could check out the same ports tree the 
package building cluster used, I'd avoid the issue entirely.

___
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: Keeping my ports tree in sync with the public pkg repo

[Baptiste Daroussin]

On Thu, Jun 12, 2014 at 06:11:13AM -0700, Darren Pilgrim wrote:
 Is there a way to determine the ports tree revision used for the current 
 public pkg repo?
 

Right now you have no way but knowing that we take a snapshot of the ports tree
at 1am UTC every wednesday and build on it

With pkg 1.3 we will add some metadata to the repo specifying the revision used
We also to plan to add a ports package so pkg install ports will install the
ports tree used to build the packages

regads,
Bapt


pgp_tnsAixj5M.pgp
Description: PGP signature

Having a problem updating my ports 9.1-RELEASE-p10 FreeBSD 9.1-RELEASE-p10 #715 r261208: Mon Jan 27 06:45:50 CST 2014 on AMD64

[Edwin L. Culp W.]

gmake  all-recursive
gmake[3]: Entering directory
`/usr/ports/graphics/libGL/work/Mesa-9.1.7/src/glsl'
Making all in builtin_compiler
gmake[4]: Entering directory
`/usr/ports/graphics/libGL/work/Mesa-9.1.7/src/glsl/builtin_compiler'
  CXX  glsl_lexer.lo
In file included from ../../../src/glsl/glsl_types.h:31,
 from ../../../src/glsl/ir.h:33,
 from ../../../src/glsl/glsl_symbol_table.h:34,
 from ../../../src/glsl/glsl_parser_extras.h:35,
 from ../../../src/glsl/ast.h:30,
 from glsl_lexer.ll:27:
../../../src/mesa/main/mtypes.h:3420: error: 'GLDEBUGPROCARB' does not name
a type
gmake[4]: *** [glsl_lexer.lo] Error 1
gmake[4]: Leaving directory
`/usr/ports/graphics/libGL/work/Mesa-9.1.7/src/glsl/builtin_compiler'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory
`/usr/ports/graphics/libGL/work/Mesa-9.1.7/src/glsl'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/graphics/libGL/work/Mesa-9.1.7/src/glsl'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/graphics/libGL/work/Mesa-9.1.7/src'
gmake: *** [all-recursive] Error 1
*** [do-build] Error code 1

I usually keep my ports up to date but I got a few days or weeks behind.
That could be part of my problem.  I am and have been using portmaster to
update and have updated most but am stumped here.

Any suggestions appreciated.

ed
http://www.facebook.com/pages/Inmobiliaria-Bienes-Raices-httpEcoManiainfo/102249989850215?sk=photos_albums
___
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

[MAINTAINER] These are my Ports after updated USES= and other necessary changes

[nemysis]

Please have a look, test as needed and commit these diffs.

I am open to comments  suggestions, and I have not forgotten my older problem 
reports either.


Earlier I missed out on ${MKDIR} variable please add it as @${MKDIR} ${DOCSDIR} 

When i have forgot to change and similar ${MKDIR} please correct this

${MKDIR} ${DOCSDIR} -- @${MKDIR} ${DOCSDIR}



Sorry for the length of this email but I am trying to be as complete as 
possible.


These changed Ports and diffs can be screened at GitHub

https://github.com/nemysis/FreeBSD_Ports/tree/master/ports-changed



These are PR with new Versions

178841 [MAINTAINER] astro/viking: update to 1.4.1

178843 [MAINTAINER] deskutils/recoll: update to 1.18.2

178844 [MAINTAINER] games/connectagram: update to 1.1.1

178845 [MAINTAINER] games/domination: update to 1.1.1.4

178846 [MAINTAINER] graphics/glfw: update to 2.7.8

178847 [MAINTAINER] games/robocode: update to 1.8.1.0

178849 [MAINTAINER] graphics/pstoedit: update to 3.62

178850 [MAINTAINER] net-p2p/qbittorrent: update to 3.0.9

17 [MAINTAINER] graphics/xsane: update to 0.999



games/iceicepenguin

This is a fix

178501: games/iceicepenguin: Needs different distfile subdir


games/speakinghangman

not more upstream

http://www.athenasoft.net/hangman/index.en.php

http://www.athenasoft.net/

RESTRICTED= License does not allow redistribution

Please delete this Port and too close these PRs

ports/171869: [NEW PORT] games/multiplik12: Educational game for learning and 
practicing the multiplication tables

ports/171870: [NEW PORT] games/visualspell: Challenges players to use reasoning 
skills to match a word



Below are some old builds from RedPorts, some build from RedPorts are expired, 
which are not committed as yet.


audio/alure

https://redports.org/buildarchive/20130527223700-44231/
depend (compiler_error in audio/jack)

- Fix docs
- Fix examples
- Trim install
- Trim pkg-plist, remove mtree



audio/hexter

- Shorten header



cad/ldraw

- Trim Makefile header
- Trim typo



comms/spandsp-devel

- Add license
- Add new Uses
- Fix docs



deskutils/xwrits

- Add license



devel/allegro-devel

- Add license
- Add dependency for graphics/png



games/BillardGL

https://redports.org/buildarchive/20130527224500-37032/

- Trim dependency for archivers/unzip
- Trim desktop entry
- Trim typo
- Trim pkg-plist, remove mtree



games/abuse_sdl

- Trim typo



games/anki

- Add WWW



games/asteroid

https://redports.org/buildarchive/20130527224300-24633/

- Trim distinfo
- Trim new Uses
- Change Homepage
- Trim pkg-plist, remove mtree



games/asteroids3d

https://redports.org/buildarchive/20130528084600-58539/

- Trim Makefile header
- Trim typo
- Trim pkg-plist, remove mtree



games/avoision

- Shorten header
- Trim comment
- Trim PLIST_FILES
- Trim docs



games/barbie_seahorse_adventures

https://redports.org/buildarchive/20130527224900-5960/

- Trim Makefile header
- Trim Desktop entry file
- Trim pkg-plist, remove mtree



games/black-box

- Trim Makefile header
- Trim Desktop entry file
- Trim install



games/bubble-chains

- Trim Makefile header
- Trim Desktop entry file


games/cretan-hubris

- Shorten header
- Add new Uses
- Trim PLIST_FILES and PLIST_DIRS



games/cutemaze

https://redports.org/buildarchive/20130527225200-47273/

- Trim Makefile header
- Add new Uses
- Remove unneeded LGPL
- Trim install
- Trim pkg-plist, remove mtree



games/empire

- Shorten header



games/fbg2

- Shorten header
- Add new Uses
- Trim PLIST_FILES and PLIST_DIRS



games/galaxis

- Shorten header
- Add license
- Trim typo



games/gemdropx

https://redports.org/buildarchive/20130527225400-9252/

- Shorten header
- Bump portrevision
- Change Icons
- Add Desktop entry file
- Remove unneeded .xvpics
- Cleanup Makefile
- Add pkg-plist

Added file(s):
- pkg-plist



games/glightoff

- Trim Makefile header
- Add desktop dependency



games/gottet

https://redports.org/buildarchive/20130527225600-43001/

- Trim Makefile header
- Trim typo
- Trim pkg-plist, remove mtree



games/help_hannahs_horse

https://redports.org/buildarchive/20130527235601-5997/

- Trim Makefile header
- Trim Desktop entry file
- Trim pkg-plist, remove mtree



games/hitori

https://redports.org/buildarchive/20130525160500-8353/

- Trim REINPLACE_CMD
- Trim typo
- Trim pkg-plist, remove mtree



games/icbm3d

https://redports.org/buildarchive/20130527235800-23838/

- Bump portrevision
- Shorten header
- Change Icons
- Add Desktop entry file
- Cleanup Makefile



games/icebreaker

https://redports.org/buildarchive/20130327001000-10001/

- Bump portrevision
- Trim master sites
- Remove dependency for graphics/netpbm
- Add Desktop entry file
- Trim REINPLACE_CMD
- Add pkg-plist

Added file(s):
- pkg-plist



games/impossible_mission_puzzle

https://redports.org/buildarchive/20130327003900-16476/

- Trim Makefile header
- Trim Desktop entry file



games/krank

- Trim Makefile header
- Symlink the icon instead of copying it

pkg has screwed up my ports

[Jamie Paul Griffin]

This morning I updated my ports tree using svn, then ran portmaster -L
to check outdated ports. portmaster was one of those ports. 

I then ran portmaster -a . it prompted me to select options from the
blue options screen, I selected pkgng support. 

Anyway, the update of portmaster failed. I ran pkg2ng, it went through
all of my ports, etc. Just following instruction that were printed to
the terminal. 

It has screwed up spamassassin to the point where I cannot even install
it now; either using make install clean, pkg install ... , portmaster
mail/p5-Mail-SpamAsassin, etc, etc. There may be others too, I can't
tell right now because my entire ports system has been corrupted and
therefore rendered useless.

i'm on a different machine now so I don't have all the errors i've been
getting available right now

i Think i'm going to have remove every single port and start again. I'm
really peed off about this. Moving forward and progressing is fine, but
there are clearly plenty of problems with this new pkg mechanism. I've
been sat here all day trying to fix the mess and i'm no further forward.
A total waste of day. Aren't these things tested properly before forcing them
upon us users - it's us that suffer. I've had to take my mail server
offline and route mail to another whilst I get this sorted. 

Surely someone else has had this issue today, or recently. ???
___
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: pkg has screwed up my ports

[Volodymyr Kostyrko]

15.10.2012 18:07, Jamie Paul Griffin wrote:

This morning I updated my ports tree using svn, then ran portmaster -L
to check outdated ports. portmaster was one of those ports.

I then ran portmaster -a . it prompted me to select options from the
blue options screen, I selected pkgng support.

Anyway, the update of portmaster failed. I ran pkg2ng, it went through
all of my ports, etc. Just following instruction that were printed to
the terminal.

It has screwed up spamassassin to the point where I cannot even install
it now; either using make install clean, pkg install ... , portmaster
mail/p5-Mail-SpamAsassin, etc, etc. There may be others too, I can't
tell right now because my entire ports system has been corrupted and
therefore rendered useless.

i'm on a different machine now so I don't have all the errors i've been
getting available right now

i Think i'm going to have remove every single port and start again. I'm
really peed off about this. Moving forward and progressing is fine, but
there are clearly plenty of problems with this new pkg mechanism. I've
been sat here all day trying to fix the mess and i'm no further forward.
A total waste of day. Aren't these things tested properly before forcing them
upon us users - it's us that suffer. I've had to take my mail server
offline and route mail to another whilst I get this sorted.

Surely someone else has had this issue today, or recently. ???


echo WITH_PKGNG=yes  /etc/make.conf

--
Sphinx of black quartz, judge my vow.
___
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: pkg has screwed up my ports

[Bryan Drewery]

On 10/15/2012 10:07 AM, Jamie Paul Griffin wrote:
 This morning I updated my ports tree using svn, then ran portmaster -L
 to check outdated ports. portmaster was one of those ports. 
 
 I then ran portmaster -a . it prompted me to select options from the
 blue options screen, I selected pkgng support. 
 

Sorry for this not being more clear. I will add a message in.

If you select PKGNG, the assumption is you have pkg installed and will
run pkg2ng to stop using the old /var/db/pkg|pkg_install format.

Selecting PKGNG option requires you run pkg2ng, otherwise portmaster
will think you have nothing installed.

 Anyway, the update of portmaster failed. I ran pkg2ng, it went through
 all of my ports, etc. Just following instruction that were printed to
 the terminal. 
 
 It has screwed up spamassassin to the point where I cannot even install
 it now; either using make install clean, pkg install ... , portmaster
 mail/p5-Mail-SpamAsassin, etc, etc. There may be others too, I can't
 tell right now because my entire ports system has been corrupted and
 therefore rendered useless.
 
 i'm on a different machine now so I don't have all the errors i've been
 getting available right now
 
 i Think i'm going to have remove every single port and start again. I'm
 really peed off about this. Moving forward and progressing is fine, but
 there are clearly plenty of problems with this new pkg mechanism. I've
 been sat here all day trying to fix the mess and i'm no further forward.
 A total waste of day. Aren't these things tested properly before forcing them
 upon us users - it's us that suffer. I've had to take my mail server
 offline and route mail to another whilst I get this sorted. 
 
 Surely someone else has had this issue today, or recently. ???
 ___
 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
 


-- 
Regards,
Bryan Drewery
bdrewery@freenode/EFNet
___
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: pkg has screwed up my ports

[Bryan Drewery]

On 10/15/2012 10:37 AM, Bryan Drewery wrote:
 On 10/15/2012 10:07 AM, Jamie Paul Griffin wrote:
 This morning I updated my ports tree using svn, then ran portmaster -L
 to check outdated ports. portmaster was one of those ports. 

 I then ran portmaster -a . it prompted me to select options from the
 blue options screen, I selected pkgng support. 

 
 Sorry for this not being more clear. I will add a message in.
 
 If you select PKGNG, the assumption is you have pkg installed and will
 run pkg2ng to stop using the old /var/db/pkg|pkg_install format.
 
 Selecting PKGNG option requires you run pkg2ng, otherwise portmaster
 will think you have nothing installed.

Need more caffeine.

Selecting PKGNG will not enable pkgng, but adding WITH_PKGNG=yes in your
make.conf WILL force pkgng, thus requiring pkg2ng be ran.

 
 Anyway, the update of portmaster failed. I ran pkg2ng, it went through
 all of my ports, etc. Just following instruction that were printed to
 the terminal. 

 It has screwed up spamassassin to the point where I cannot even install
 it now; either using make install clean, pkg install ... , portmaster
 mail/p5-Mail-SpamAsassin, etc, etc. There may be others too, I can't
 tell right now because my entire ports system has been corrupted and
 therefore rendered useless.

 i'm on a different machine now so I don't have all the errors i've been
 getting available right now

 i Think i'm going to have remove every single port and start again. I'm
 really peed off about this. Moving forward and progressing is fine, but
 there are clearly plenty of problems with this new pkg mechanism. I've
 been sat here all day trying to fix the mess and i'm no further forward.
 A total waste of day. Aren't these things tested properly before forcing them
 upon us users - it's us that suffer. I've had to take my mail server
 offline and route mail to another whilst I get this sorted. 

 Surely someone else has had this issue today, or recently. ???
 ___
 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

 
 


-- 
Regards,
Bryan Drewery
bdrewery@freenode/EFNet
___
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: Adding licensing info to my ports: some questions

[Chad Perrin]

On Wed, Jan 18, 2012 at 04:13:11PM -0500, Graham Todd wrote:
 
 I doubt this simpler approach would be ITIL compliant ;) but since
 that is not a goal and the bulk of anything to do with licenses involves
 lawyers anyway, the ports/pkg system should probably try to do as little
 as possible regarding claims and interpretation. Surely keeping copies
 of licenses in an easy to find location doesn't equate to making any
 legal claim ?  NB: I am not a lawyer :)

I'm pretty dismayed by the ignore it and it'll go away attitude toward
licensing in much of the open source world.  How exactly do people think
that a willful ignorance defense would in any way protect the FreeBSD
project from copyright/license claims where an attempt at due diligence
(that is, finding license information with the project files and making
note of it in the port Makefile) to the reasonable best of our ability
would somehow make the project liable?  That doesn't make any sense, and
unless there are some lawyers who can cite caselaw to the contrary I
think the safest bet is probably an attempt to be transparent and
informative, with a disclaimer attached.

Of course, I'm not a lawyer either, and this is not intended as legal
advice.  It's just an expression of frustration at the way everybody
seems to think intentionally ignoring licensing will somehow make
copyright and license claims invalid.

-- 
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
___
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: Adding licensing info to my ports: some questions

[Torfinn Ingolfsen]

Hi,

On Wed, Jan 18, 2012 at 12:13 AM, Doug Barton do...@freebsd.org wrote:

 On 01/17/2012 14:35, Torfinn Ingolfsen wrote:
  Anything can go wrong, but it is (IMO) quite easy to state the intention
 of
  the FreeBSD Project in this case.

 You're making the very common mistake of assuming that the law has
 anything to do with reality. It doesn't. The fact that we're making
 claims about legal issues opens the project up to a wide array of hairy
 liability problems. It doesn't matter how baseless the lawsuit is,
 sometimes just filing the suit creates enough damage to kill the thing
 sued.

 No, I'm aware that in some parts of the world, law practice is far away
from the intention of the law. Luckily, it isn't that bad all over the
world, not yet anyway.
However, I think that anyone who tries to _do_ something should have the
courage / balls / whatever to stand up and try to make the best he or she
can, with the means available.
Otherwise, we could all just go and hide under a stone, and nothing would
be done.

Now, can we get back to our regular schedule, please?
-- 
Regards,
Torfinn Ingolfsen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Adding licensing info to my ports: some questions

[Johan van Selst]

Nikola Lečić wrote:
 Anyway, it wasn't clear from the bsd.licenses.mk that we should use
 'multi' in situations of 'any later version'. This means that all
 licensing info of eg. GPL2+ ports must be updated when GPL4 appears...

No, we should not use this. Not just because of the potential of having
to check and correct every port when GPLv4 appears. In my book,
licenced under GPLv2 or GPLv3 is something fundamentally different
from licenced under GPLv2 or any later version. The licence framework
should be able to make this distinction.

Another issue is that the licence infrastructure seems to be making
statements about the licence of an application, while the committers
only tend to look at individual source packages. What would be the
licence of an application whose source is published under BSD licence,
but that is linked with both GPv3 and OpenSSL-libraries?

I tend to agree with Doug and others that it is probably better to scrap
the entire idea. Making assertions about licences and what is accepted
is a hairy field, best left to experts.


Regards,
Johan


pgpqnD8hLmBzH.pgp
Description: PGP signature

Re: Adding licensing info to my ports: some questions

[Graham Todd]

On 01/18/2012 04:34, Johan van Selst wrote:
 Nikola Lečić wrote:
 Anyway, it wasn't clear from the bsd.licenses.mk that we should
 use 'multi' in situations of 'any later version'. This means that
 all licensing info of eg. GPL2+ ports must be updated when GPL4
 appears...
 
 No, we should not use this. Not just because of the potential of
 having to check and correct every port when GPLv4 appears. In my
 book, licenced under GPLv2 or GPLv3 is something fundamentally
 different from licenced under GPLv2 or any later version. The
 licence framework should be able to make this distinction.
 
 Another issue is that the licence infrastructure seems to be making 
 statements about the licence of an application, while the committers 
 only tend to look at individual source packages. What would be the 
 licence of an application whose source is published under BSD
 licence, but that is linked with both GPv3 and OpenSSL-libraries?
 
 I tend to agree with Doug and others that it is probably better to
 scrap the entire idea. Making assertions about licences and what is
 accepted is a hairy field, best left to experts.

I hope this effort is not completely abandoned since it does seem to
offer an easy way to get a general sense of the license status of a
system, jail or vm. What about a more explicitly passive approach that
does not make assertions about an application's overall license (c.f.
linking issues) or the user's acceptance but just makes such license
files as do exist easier to find?

If such a simple license tracking feature is useful (even if not
suitable for management, compliance, budgeting, license acceptance and
the like) then something that would grab the locations of license
documents in a port's source files and copies the relevant files into a
default license location /usr/local/share/licenses/port/ would be
enough. Would this ports knob feature (LICENSE_=) disappear if the
project were scrapped?

I doubt this simpler approach would be ITIL compliant ;) but since
that is not a goal and the bulk of anything to do with licenses involves
lawyers anyway, the ports/pkg system should probably try to do as little
as possible regarding claims and interpretation. Surely keeping copies
of licenses in an easy to find location doesn't equate to making any
legal claim ?  NB: I am not a lawyer :)

cheers,


ps:

ls -1 /usr/local/share/licenses/*/LICENSE | wc -l
 221
ls -1 /usr/local/share/licenses/*/*  | grep -E MIT|BSD |wc -l
 86
ls -1 /usr/local/share/licenses/*/*  | grep -E LGPL*|GPL* |wc -l
 116

Of course, the above system has 1200 ports installed so there's a ways
to go before one could say tracking was happening :)

___
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: Adding licensing info to my ports: some questions

[Vitaly Magerya]

Eitan Adler wrote:
 1) Will licensing section ever appear in the Porters Handbook? :-)
 
 Yes

Is someone actually working on it? If so, and is there some sort of
target timeline?

Back in 2010 when the framework was introduced, my general impression
was that maintainers where advised to wait with the adoption until that
chapter is written...
___
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: Adding licensing info to my ports: some questions

[Doug Barton]

On 01/17/2012 03:56, Vitaly Magerya wrote:
 Eitan Adler wrote:
 1) Will licensing section ever appear in the Porters Handbook? :-)

 Yes
 
 Is someone actually working on it? If so, and is there some sort of
 target timeline?
 
 Back in 2010 when the framework was introduced, my general impression
 was that maintainers where advised to wait with the adoption until that
 chapter is written...

Personally I think we should scrap the whole thing. It is an interesting
idea, but the implementation has never fleshed out. It's also completely
unclear what any of it means from an actual legal standpoint, and
personally I'm not convinced that we aren't making things worse for the
project by doing this.


Doug

-- 

It's always a long day; 86400 doesn't fit into a short.

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

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

Re: Adding licensing info to my ports: some questions

[Chad Perrin]

On Tue, Jan 17, 2012 at 10:38:08AM -0800, Doug Barton wrote:
 On 01/17/2012 03:56, Vitaly Magerya wrote:
  Eitan Adler wrote:
  1) Will licensing section ever appear in the Porters Handbook? :-)
 
  Yes
  
  Is someone actually working on it? If so, and is there some sort of
  target timeline?
  
  Back in 2010 when the framework was introduced, my general impression
  was that maintainers where advised to wait with the adoption until that
  chapter is written...
 
 Personally I think we should scrap the whole thing. It is an interesting
 idea, but the implementation has never fleshed out. It's also completely
 unclear what any of it means from an actual legal standpoint, and
 personally I'm not convinced that we aren't making things worse for the
 project by doing this.

How?  I don't see the problem that makes things worse, I guess.

-- 
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
___
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: Adding licensing info to my ports: some questions

[Chris Rees]

On 17 Jan 2012 18:43, Chad Perrin c...@apotheon.net wrote:

 On Tue, Jan 17, 2012 at 10:38:08AM -0800, Doug Barton wrote:
  On 01/17/2012 03:56, Vitaly Magerya wrote:
   Eitan Adler wrote:
   1) Will licensing section ever appear in the Porters Handbook? :-)
  
   Yes
  
   Is someone actually working on it? If so, and is there some sort of
   target timeline?
  
   Back in 2010 when the framework was introduced, my general impression
   was that maintainers where advised to wait with the adoption until
that
   chapter is written...
 
  Personally I think we should scrap the whole thing. It is an interesting
  idea, but the implementation has never fleshed out. It's also completely
  unclear what any of it means from an actual legal standpoint, and
  personally I'm not convinced that we aren't making things worse for the
  project by doing this.

 How?  I don't see the problem that makes things worse, I guess.

Well... the author and maintainer of the code isn't around any more.

Chris
___
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: Adding licensing info to my ports: some questions

[Warren Block]

On Tue, 17 Jan 2012, Chad Perrin wrote:


On Tue, Jan 17, 2012 at 10:38:08AM -0800, Doug Barton wrote:

On 01/17/2012 03:56, Vitaly Magerya wrote:

Eitan Adler wrote:

1) Will licensing section ever appear in the Porters Handbook? :-)


Yes


Is someone actually working on it? If so, and is there some sort of
target timeline?

Back in 2010 when the framework was introduced, my general impression
was that maintainers where advised to wait with the adoption until that
chapter is written...


Personally I think we should scrap the whole thing. It is an interesting
idea, but the implementation has never fleshed out. It's also completely
unclear what any of it means from an actual legal standpoint, and
personally I'm not convinced that we aren't making things worse for the
project by doing this.


How?  I don't see the problem that makes things worse, I guess.


In my not-a-lawyer view, I wonder if it puts some responsibility for 
accurately representing a license on FreeBSD and the ports system.  We 
used this software because the FreeBSD ports system said the license was 
compatible for our use.  Now it turns out otherwise, and we have 
millions in damages...


There's the potential for someone to intentionally put the wrong license 
in a port to create such a situation.  And to protect against that, will 
committers have to verify the license?

___
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: Adding licensing info to my ports: some questions

[Torfinn Ingolfsen]

Hello,

On Tue, Jan 17, 2012 at 8:46 PM, Warren Block wbl...@wonkity.com wrote:

 On Tue, 17 Jan 2012, Chad Perrin wrote:

  On Tue, Jan 17, 2012 at 10:38:08AM -0800, Doug Barton wrote:

 On 01/17/2012 03:56, Vitaly Magerya wrote:

 Eitan Adler wrote:

 1) Will licensing section ever appear in the Porters Handbook? :-)


 Yes


 Is someone actually working on it? If so, and is there some sort of
 target timeline?

 Back in 2010 when the framework was introduced, my general impression
 was that maintainers where advised to wait with the adoption until that
 chapter is written...


 Personally I think we should scrap the whole thing. It is an interesting
 idea, but the implementation has never fleshed out. It's also completely
 unclear what any of it means from an actual legal standpoint, and
 personally I'm not convinced that we aren't making things worse for the
 project by doing this.


 How?  I don't see the problem that makes things worse, I guess.


 In my not-a-lawyer view, I wonder if it puts some responsibility for
 accurately representing a license on FreeBSD and the ports system.  We
 used this software because the FreeBSD ports system said the license was
 compatible for our use.  Now it turns out otherwise, and we have millions
 in damages...

 There's the potential for someone to intentionally put the wrong license
 in a port to create such a situation.  And to protect against that, will
 committers have to verify the license?


But surely this framework is for information purposes only?
With standard disclaimers:
if you really want to be sure, please check the official source, things
might have changed since the port was last updated
buyer (or porst user) beware

Anything can go wrong, but it is (IMO) quite easy to state the intention of
the FreeBSD Project in this case.
But that requires that someone writes the chapter about this in the Porters
Handbook...
-- 
Regards,
Torfinn Ingolfsen
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Adding licensing info to my ports: some questions

[Doug Barton]

On 01/17/2012 14:35, Torfinn Ingolfsen wrote:
 Anything can go wrong, but it is (IMO) quite easy to state the intention of
 the FreeBSD Project in this case.

You're making the very common mistake of assuming that the law has
anything to do with reality. It doesn't. The fact that we're making
claims about legal issues opens the project up to a wide array of hairy
liability problems. It doesn't matter how baseless the lawsuit is,
sometimes just filing the suit creates enough damage to kill the thing
sued.

For example:

@${ECHO_MSG} ===  License ${_LICENSE} accepted by the user


*shudder*

Doug

-- 

It's always a long day; 86400 doesn't fit into a short.

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price.  :)  http://SupersetSolutions.com/

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

Adding licensing info to my ports: some questions

[Nikola Lečić]

Hello,

I'm about to add licensing info to all my 25 ports. I hoped that a
chapter dedicated to licensing issues would appear in the Porters
Handbook, but since this hasn't happened so far, I decided to try
without it.

Here are my questions; sorry if some of them are already answered in
the past.

1) Will licensing section ever appear in the Porters Handbook? :-)

2) Should I mark the ports that explicitly state X11 with MIT?

3) Intentionally no difference between 2- and 3-clause BSD?

4) How should I state eg. LGPL21 or any later version or GPL2
   only i.e. no later version?

5) What if licensing info differs for entire source file and actually
   installed files? In textproc/kmfl-sil-ezra source file, the font is
   licensed OFL and the keyboard layout X11; the port installs only
   keyboard layout. Should I state just MIT in the Makefile?

6) I need three new items added to the licenses database because they
   should be considered as 'known' licenses and thus belonging to the
   'Case 1' in bsd.licenses.mk. There are: Common Public License, SIL
   Open Font License and Public Domain [non-license]. I'd gladly
   submit a PR, but I'd appreciate if someone could check this first,
   especially _LICENSE_GROUPS_* including COPYFREE status.

   6a) CPL:
  _LICENSE_NAME_CPL=  Common Public License
  _LICENSE_GROUPS_CPL=FSF

http://en.wikipedia.org/wiki/Common_Public_License
http://www.gnu.org/licenses/license-list.en.html#CommonPublicLicense10

  As for this license, the software in question (textproc/teckit)
  is licensed GLPLv2.1+ or CPLv0.5+. However, the CPL version
  approved on gnu.org, used in NetBSD... is 1.0. Should we make
  any difference between CPL versions because of this? Or just to
  use LICENSE_TEXT?

  (Btw, the Wikipedia article on CPL states that this license is
  OSI-approved, but I can't find it here:
  http://www.opensource.org/licenses/category.)

   6b) OFL:
  _LICENSE_NAME_OFL=  SIL Open Font License
  _LICENSE_GROUPS_OFL=FSF OSI

 http://en.wikipedia.org/wiki/SIL_Open_Font_License
 http://www.gnu.org/licenses/license-list.en.html#SILOFL
 http://www.opensource.org/licenses/OFL-1.1

   6c) PD[?]:
  _LICENSE_NAME_PD=   Public Domain
  _LICENSE_GROUPS_PD= FSF GPL

 http://www.gnu.org/licenses/license-list.en.html#PublicDomain
 
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/licenses/public-domain?only_with_tag=MAIN

Many thanks in advance,
-- 
Nikola Lečić = Никола Лечић
fingerprint : FEF3 66AF C90E EDC3 D878  7CDC 956D F4AB A377 1C9B



pgpxqZlAu9o2O.pgp
Description: PGP signature

Re: Adding licensing info to my ports: some questions

[Eitan Adler]

2012/1/16 Nikola Lečić nikola.le...@anthesphoria.net:
 Hello,

 I'm about to add licensing info to all my 25 ports. I hoped that a
 chapter dedicated to licensing issues would appear in the Porters
 Handbook, but since this hasn't happened so far, I decided to try
 without it.

 Here are my questions; sorry if some of them are already answered in
 the past.

 1) Will licensing section ever appear in the Porters Handbook? :-)

Yes

 2) Should I mark the ports that explicitly state X11 with MIT?

Yes, or you may break the build. Not that I've ever done that of course ;)

 3) Intentionally no difference between 2- and 3-clause BSD?

I hope not. We should probably have a BSD2, BSD3, and BSD4 license.
For now mark it with a comment (or offer a patch to the db file too)

 4) How should I state eg. LGPL21 or any later version or GPL2
   only i.e. no later version?

 5) What if licensing info differs for entire source file and actually
   installed files? In textproc/kmfl-sil-ezra source file, the font is
   licensed OFL and the keyboard layout X11; the port installs only
   keyboard layout. Should I state just MIT in the Makefile?

LICENSE_COMB=multi I think

 6) I need three new items added to the licenses database because they
   should be considered as 'known' licenses and thus belonging to the
   'Case 1' in bsd.licenses.mk. There are: Common Public License, SIL
   Open Font License and Public Domain [non-license]. I'd gladly
   submit a PR, but I'd appreciate if someone could check this first,
   especially _LICENSE_GROUPS_* including COPYFREE status.

Please submit this as a patch in a PR and email me. I'll make sure
they get added.

Common Public License is not copyfree.
SIL Open Font License is not copyfree.
Putting something in the Public Domain doesn't work in any meaningful
sense and is not a license.

I am not a lawyer and I am not giving legal advice.
-- 
Eitan Adler
___
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: Adding licensing info to my ports: some questions

[Nikola Lečić]

On Mon, Jan 16, 2012 at 08:14:57PM -0500
  in CAF6rxg=n1ocjoyfg40k8fkuzbtms8s_r8v7vclocapzfmwq...@mail.gmail.com
  Eitan Adler li...@eitanadler.com wrote:

 2012/1/16 Nikola Lečić nikola.le...@anthesphoria.net:
[...]
  3) Intentionally no difference between 2- and 3-clause BSD?
 
 I hope not. We should probably have a BSD2, BSD3, and BSD4 license.
 For now mark it with a comment (or offer a patch to the db file too)

Ok. What should happen with existing BSD in that case?

  4) How should I state eg. LGPL21 or any later version or GPL2
    only i.e. no later version?
 
  5) What if licensing info differs for entire source file and actually
    installed files? In textproc/kmfl-sil-ezra source file, the font is
    licensed OFL and the keyboard layout X11; the port installs only
    keyboard layout. Should I state just MIT in the Makefile?
 
 LICENSE_COMB=multi I think

I see, but does 'multi' applies to distfile which is just downloaded
and unzipped or to installed files (and eo ipso to the FreeBSD
package)?

Anyway, it wasn't clear from the bsd.licenses.mk that we should use
'multi' in situations of 'any later version'. This means that all
licensing info of eg. GPL2+ ports must be updated when GPL4 appears...

  6) I need three new items added to the licenses database because they
    should be considered as 'known' licenses and thus belonging to the
    'Case 1' in bsd.licenses.mk. There are: Common Public License, SIL
    Open Font License and Public Domain [non-license]. I'd gladly
    submit a PR, but I'd appreciate if someone could check this first,
    especially _LICENSE_GROUPS_* including COPYFREE status.
 
 Please submit this as a patch in a PR and email me. I'll make sure
 they get added.

Will do.

 Common Public License is not copyfree.
 SIL Open Font License is not copyfree.

Ok, thanks.

 Putting something in the Public Domain doesn't work in any meaningful
 sense and is not a license.

converters/base64 is public domain (see COPYING from its distfile).
Do you mean that Public Domain shouldn't be added to the licenses
database? NetBSD has it.

Thanks,
-- 
Nikola Lečić = Никола Лечић
fingerprint : FEF3 66AF C90E EDC3 D878  7CDC 956D F4AB A377 1C9B



pgpZeNEDgraCv.pgp
Description: PGP signature

Re: Adding licensing info to my ports: some questions

[Eitan Adler]

2012/1/16 Nikola Lečić nikola.le...@anthesphoria.net:
 On Mon, Jan 16, 2012 at 08:14:57PM -0500
  in CAF6rxg=n1ocjoyfg40k8fkuzbtms8s_r8v7vclocapzfmwq...@mail.gmail.com
  Eitan Adler li...@eitanadler.com wrote:

 2012/1/16 Nikola Lečić nikola.le...@anthesphoria.net:
 [...]
  3) Intentionally no difference between 2- and 3-clause BSD?

 I hope not. We should probably have a BSD2, BSD3, and BSD4 license.
 For now mark it with a comment (or offer a patch to the db file too)

 Ok. What should happen with existing BSD in that case?

Leave it (cause some ports/configurations might break) but deprecate it.
Note that I am not on portmgr ;)

 I see, but does 'multi' applies to distfile which is just downloaded
 and unzipped or to installed files (and eo ipso to the FreeBSD
 package)?

 Anyway, it wasn't clear from the bsd.licenses.mk that we should use
 'multi' in situations of 'any later version'. This means that all
 licensing info of eg. GPL2+ ports must be updated when GPL4 appears...

I am not certain about this.

 Putting something in the Public Domain doesn't work in any meaningful
 sense and is not a license.

 converters/base64 is public domain (see COPYING from its distfile).
 Do you mean that Public Domain shouldn't be added to the licenses
 database? NetBSD has it.

This list is the wrong location to discuss this issue so any followup
should happen off-list.


-- 
Eitan Adler
___
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: Adding licensing info to my ports: some questions

[Chad Perrin]

On Tue, Jan 17, 2012 at 05:40:35AM +0300, Nikola Lečić wrote:
 On Mon, Jan 16, 2012 at 08:14:57PM -0500 Eitan Adler [email address
 elided] wrote:
  2012/1/16 Nikola Lečić nikola.le...@anthesphoria.net:
  
   6) I need three new items added to the licenses database because they
     should be considered as 'known' licenses and thus belonging to the
     'Case 1' in bsd.licenses.mk. There are: Common Public License, SIL
     Open Font License and Public Domain [non-license]. I'd gladly
     submit a PR, but I'd appreciate if someone could check this first,
     especially _LICENSE_GROUPS_* including COPYFREE status.
  
  Please submit this as a patch in a PR and email me. I'll make sure
  they get added.
 
 Will do.
 
  Common Public License is not copyfree.
  SIL Open Font License is not copyfree.
 
 Ok, thanks.

There are lists of licenses certified as complying with the Copyfree
Standard Definition and licenses explicitly rejected at the Copyfree
Initiative website:

http://copyfree.org/licenses

http://copyfree.org/rejected

I hope this helps in the future.  There are contact links on the site you
can use to send messages if you have other licenses than listed there you
want to ask about.  It might be worthwhile to check the page for the
Copyfree Standard Definition when wondering about a given license, if it
is not on one of those lists, though:

http://copyfree.org/standard


 
  Putting something in the Public Domain doesn't work in any meaningful
  sense and is not a license.
 
 converters/base64 is public domain (see COPYING from its distfile).
 Do you mean that Public Domain shouldn't be added to the licenses
 database? NetBSD has it.

It seems like it would be useful to have a public domain category of
some kind, from where I'm sitting, with the understanding that it may not
mean anything useful depending on jurisdiction.  Beyond that, I probably
shouldn't say anything about it on this list.  The applicability of
plain ol' public domain dedications can be a contentious topic.

-- 
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
___
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: giving up maintainership for all my ports

[Philip M. Gollucci]

On 10/31/11 21:45, Russell Jackson wrote:
 textproc/rubygem-augeas
now owned by ruby@



-- 

1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354
Member,   Apache Software Foundation
Committer,FreeBSD Foundation
Consultant,   P6M7G8 Inc.
Director Operations,  Ridecharge Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.



signature.asc
Description: OpenPGP digital signature

giving up maintainership for all my ports

[Russell Jackson]

These are all up for grabs.

sysutils/puppet
textproc/augeas
textproc/rubygem-augeas
sysutils/mcollective

--
Russell A. Jackson r...@csub.edu
Network Analyst
California State University, Bakersfield
___
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: giving up maintainership for all my ports

[Steve Wills]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

On 10/31/11 17:45, Russell Jackson wrote:
 These are all up for grabs.
 
 sysutils/puppet
 textproc/augeas
 textproc/rubygem-augeas
 sysutils/mcollective
 

I've taken sysutils/puppet and sysutils/mcollective.

Thanks, hope to see you back soon!
Steve
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (FreeBSD)

iQEcBAEBAgAGBQJOryMnAAoJEPXPYrMgexuhKPkH/2TjCVS+y1GnTJ2DttN2dtgI
OWhtIosb6D1oGjcKZL+D7WZBMuz99aPfVUfbY5T+9VX3QDxbj4uqkmc02s+u051E
Wx5VvUy9/ePTUDv4n0xx+nqJjYMoNJfBlotJSZSXBQC0AHBUbYBXMKdFK23HqRmc
0nz5dISfM4mtLpETJs6ouCr+ZXxV7VQCRx39beYgJNaO6slVtumNbeFaalWmkBJO
OIgI8EFuTOa2CXCryYI4Dsjc2bls+3MPqbHgHgkvChNjrw47ggYrcTrR56BE+9o2
mVhlTPnQnKYL9lnn0/FE4L1LP7uLhqJJ6vLnLsjdosXB+O1eypkZC6/FIY/TxE4=
=ST+/
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Fwd: Re: Dropping maintainership of my ports

[Ruslan Mahmatkhanov]

Hi!
So can pleas anybody assign me as maintainer for this ports?

 Исходное сообщение 
Тема: Re: Dropping maintainership of my ports
Дата: Wed, 27 Apr 2011 09:12:54 +0400
От: Ruslan Mahmatkhanov cvs-...@yandex.ru
Кому: freebsd-ports@freebsd.org

27.04.2011 05:43, Charlie Kester пишет:


Well, due to some serious philosophical differences re these
deprecation campaigns and what seems to be resistance to any further
discussion, I don't think I can continue working with the committers.
So I'm stepping down.

If no one else wants to maintain them, please reset the maintainer of the
following ports to po...@freebsd.org:



I'm interesting in maintaing of this ports:


multimedia/gpodder
sysutils/rdup


--
Regards,
Ruslan
___
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: Fwd: Re: Dropping maintainership of my ports

[Ruslan Mahmatkhanov]

03.05.2011 00:13, Greg Larkin пишет:


multimedia/gpodder
sysutils/rdup




Hi Ruslan,

I just assigned those ports to you.  Thank you for volunteering!

Cheers,
Greg


Thank you, Greg!

--
Regards,
Ruslan
___
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: Fwd: Re: Dropping maintainership of my ports

[Greg Larkin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 5/2/11 3:55 PM, Ruslan Mahmatkhanov wrote:
 Hi!
 So can pleas anybody assign me as maintainer for this ports?
 
  Исходное сообщение 
 Тема: Re: Dropping maintainership of my ports
 Дата: Wed, 27 Apr 2011 09:12:54 +0400
 От: Ruslan Mahmatkhanov cvs-...@yandex.ru
 Кому: freebsd-ports@freebsd.org
 
 27.04.2011 05:43, Charlie Kester пишет:

 Well, due to some serious philosophical differences re these
 deprecation campaigns and what seems to be resistance to any further
 discussion, I don't think I can continue working with the committers.
 So I'm stepping down.

 If no one else wants to maintain them, please reset the maintainer of the
 following ports to po...@freebsd.org:

 
 I'm interesting in maintaing of this ports:
 
 multimedia/gpodder
 sysutils/rdup
 

Hi Ruslan,

I just assigned those ports to you.  Thank you for volunteering!

Cheers,
Greg
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2/EHEACgkQ0sRouByUApAy5QCgqmhRoaaPUyrgdtWmSmg84RPJ
UE4An0Y8soBkAfbcq+2x0OdWR/w0k6A6
=4GI1
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Fwd: Re: Dropping maintainership of my ports

[Anton Shterenlikht]

On Mon, May 02, 2011 at 04:13:37PM -0400, Greg Larkin wrote:
  If no one else wants to maintain them, please reset the maintainer of the
  following ports to po...@freebsd.org:
 
  
  I'm interesting in maintaing of this ports:
  
  multimedia/gpodder
  sysutils/rdup
  
 
 Hi Ruslan,
 
 I just assigned those ports to you.  Thank you for volunteering!

I'd like to take maintainership of

astro/xearth
textproc/urlview

-- 
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
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: Fwd: Re: Dropping maintainership of my ports

[Mark Linimon]

On Mon, May 02, 2011 at 10:01:48PM +0100, Anton Shterenlikht wrote:
 I'd like to take maintainership of
 
 astro/xearth
 textproc/urlview

done.

mcl
___
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: Dropping maintainership of my ports

[perryh]

Eitan Adler li...@eitanadler.com wrote:

  I've been told that we shouldn't be looking for reasons
  to save any unmaintained port,

 What you have been told is no-one steps up to (a) fix the
 problem, (b) take maintainership and (c) _continue_ with
 maintainership ...

 If you are stepping up to do the work that is great and we thank
 you for that! We we don't want is people who only volunteer for
 part (a) and don't continue with (b) and (c).

  and I was specifically told this in response to my
  efforts to identify ports that have a lot of users.

 Merely finding popular ports does not help. We need people
 who have the time and energy to maintain the ports.

My reading was that Charlie _was_ stepping up to do the work --
all 3 parts of it.  Since there weren't any unmaintained ports that
he personally uses, he was volunteering to take on some that he does
_not_ personally use, as a service to the community.  In order to
achieve The Greatest Good For The Greatest Number (TM), he wanted
a way to identify popular unmaintained ports.  His proposed method
of finding out _where his efforts would do the most good for the
community_ was met not with constructive suggestions, nor even mere
indifference, but with outright hostility.  Can you blame him for
getting fed up, especially since this is apparently not the first
time he has encountered that sort of attitude from those who should
know better?

 I do not want to say that we are a volunteer project and as such
 are forgiven  however such a model does change how we must do
 things ...

FreeBSD is indeed a volunteer project.  Driving away would-be
volunteers like Charlie -- and others who will now hesitate to take
on port maintainership after reading how he has been treated -- is
not in the Project's best interest.  I think several contributors
to this thread owe both Charlie and the community an apology.
___
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: Dropping maintainership of my ports

[Charlie Kester]

On Tue 26 Apr 2011 at 22:15:58 PDT Zhihao Yuan wrote:

On Tue, Apr 26, 2011 at 8:43 PM, Charlie Kester corky1...@comcast.net wrote:


Well, due to some serious philosophical differences re these
deprecation campaigns and what seems to be resistance to any further
discussion, I don't think I can continue working with the committers.
So I'm stepping down.

If no one else wants to maintain them, please reset the maintainer of the
following ports to po...@freebsd.org:

audio/mcplay
deskutils/osmo
deskutils/teapot
devel/argtable
devel/egypt
devel/gengetopt
devel/libXGP
devel/libYGP
finance/xinvest
finance/xquote
graphics/box
graphics/boxer
graphics/fly
graphics/sng
math/ised
misc/vifm
misc/xsw
multimedia/gpodder
multimedia/openshot
multimedia/photofilmstrip
security/beecrypt
security/ccrypt
security/nettle
security/ranpwd
sysutils/dircomp
sysutils/gaffitter
sysutils/iextract
sysutils/lookat
sysutils/moreutils
sysutils/moreutils-parallel
sysutils/ncdu
sysutils/rdup
textproc/tdhkit
x11/fbpanel


O-o-ok... philosophical differences.

audio/mcplay and the 3 multimedia-related ports, + fbpanel, have many
users, AFAIK, and require much works. We need to someone to take them
soon.


I don't know what you mean by requires much works.  The only ones of
these ports that are not up-to-date are xquote and nettle. 


There is already an open PR to update nettle.  All it needs is some
attention from a committer. 


Frankly, xquote should be deprecated, as it's an old-style Motif app
that's so ugly I'll bet no one uses it.  I only took it (and the related
xinvest) because they got reinstated after I pointed out they were still
fetchable at a new location.

Everything else is in good shape.

I've been told that we shouldn't be looking for reasons to save any
unmaintained port, and I was specifically told this in response to my
efforts to identify ports that have a lot of users.  So I don't think
current policy supports the conclusion that we need to find someone to
take them soon.

There, in a nutshell, you have the philosophical disagreement which led
to my decision to be done with ports.  


If the powers-that-be want to deprecate all of these and lighten the
load on the system and themselves, I no longer care.  I know how to
download a tarball and run through the configure/make/install routine,
so I'll still be able to run the software I need.  I thought I'd lend a
hand to those who don't have those skills, but it doesn't seem that this
contribution is welcomed or appreciated.  There are too many ports!

(Sorry if I'm ranting, I am still very angry about all this.)
___
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: Dropping maintainership of my ports

[Gary Kline]

sorry for the top post, but shouolder is killing me.

idea 1: can the 'summer of code' guys help us out with this.

idea 2.  why oh why can we not live with the fbsd and debian
paradigm?

the reason i've kept my domain here at home is because i like the
flexibility i see.  but keeping ports current is getting to be 
impossible.  there are too many distros of every open src os and
maybe if net and free [RE]-hjoined arms that 3rd idea would work.

i'm sure that many of you guys kno w that aristotle was a polymath;
he was as sharp as anybody i have ever studied.  his highest
'virtue' was pragmatism.given the headaches with maintaining
ports, and much more, isn' t it time to look in new directions?

idea 4.  axe the number of ports.  if person x or y want to maintain
a port of his ow n , outstanding.  he can post a note to the lists.

idea 5.  beging a completely separate, independent group for
orphaned ports [ for free, net, debian, ubuntu, redhat, foobar
opsys.   


a last note: i started out as a porter.  loved i t and excelled at
it.  but it never was easy.  it's still 3/2 * bear|bitch|swine.
ergo, i know why many of this list and org are slowing or dropping
out.

Enuf,

-g
.




On Tue, Apr 26, 2011 at 06:43:43PM -0700, Charlie Kester wrote:
 Date: Tue, 26 Apr 2011 18:43:43 -0700
 From: Charlie Kester corky1...@comcast.net
 Subject: Dropping maintainership of my ports
 To: freebsd-ports@freebsd.org
 Mail-Followup-To: freebsd-ports@freebsd.org
 X-Mailer: Mutt 1.4.2.3i
 
 
 Well, due to some serious philosophical differences re these
 deprecation campaigns and what seems to be resistance to any further
 discussion, I don't think I can continue working with the committers.
 So I'm stepping down.
 
 If no one else wants to maintain them, please reset the maintainer
 of the following ports to po...@freebsd.org:
 
 audio/mcplay
 deskutils/osmo
 deskutils/teapot
 devel/argtable
 devel/egypt
 devel/gengetopt
 devel/libXGP
 devel/libYGP
 finance/xinvest
 finance/xquote
 graphics/box
 graphics/boxer
 graphics/fly
 graphics/sng
 math/ised
 misc/vifm
 misc/xsw
 multimedia/gpodder
 multimedia/openshot
 multimedia/photofilmstrip
 security/beecrypt
 security/ccrypt
 security/nettle
 security/ranpwd
 sysutils/dircomp
 sysutils/gaffitter
 sysutils/iextract
 sysutils/lookat
 sysutils/moreutils
 sysutils/moreutils-parallel
 sysutils/ncdu
 sysutils/rdup
 textproc/tdhkit
 x11/fbpanel
 
 
 ___
 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

-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
   Journey Toward the Dawn, E-Book: http://www.thought.org
  The 7.98a release of Jottings: http://jottings.thought.org

___
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: Dropping maintainership of my ports

[John Marino]

On 4/27/2011 8:09 AM, Charlie Kester wrote:


I've been told that we shouldn't be looking for reasons to save any
unmaintained port, and I was specifically told this in response to my
efforts to identify ports that have a lot of users.  So I don't think
current policy supports the conclusion that we need to find someone to
take them soon.

There, in a nutshell, you have the philosophical disagreement which led
to my decision to be done with ports.


I skimmed the entire conversation this morning.  The summary is you have 
an opinion that apparently nobody else shares.


I maintain 7 ports.  The majority of these ports had already been 
deleted years ago, or should have already been deprecated.  So after 
years, somebody (me) showed up with enough motivation to resurrect the 
ports.  That's all people are saying: If the port is important enough, 
somebody will step up to save it or resurrect it.  If that doesn't 
happen, then it doesn't deserve to be in the tree once it doesn't build 
anymore.




If the powers-that-be want to deprecate all of these and lighten the
load on the system and themselves, I no longer care.  I know how to
download a tarball and run through the configure/make/install routine,
so I'll still be able to run the software I need.  I thought I'd lend a
hand to those who don't have those skills, but it doesn't seem that this
contribution is welcomed or appreciated.  There are too many ports!

(Sorry if I'm ranting, I am still very angry about all this.)


Obviously the maintenance of ports is appreciated and welcomed.  You're 
just sulking because your idea of identifying popular ports wasn't met 
with enthusiasm.  If the port really is popular, somebody will take it 
over, I'm sure.


I don't know you, or your history of contributions, etc, so all I can 
judge is what I read today.  I don't think this reaction shows a lot of 
character.


Anyway, I'm sure your wish of returning all the ports to nobody will be 
granted and life will go on.  As a FreeBSD user, thanks for effort that 
you did in the past.


Regards,
John



___
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: Dropping maintainership of my ports

[Charlie Kester]

On Tue 26 Apr 2011 at 23:27:40 PDT John Marino wrote:


You're just sulking because your idea of identifying popular ports
wasn't met with enthusiasm.  



No, it's more than that.  I got the distinct impression that many of the
committers would be unhappy if I took maintainership of some of the
ports I might identify as popular, because it would interfere with
their plans to trim the portstree.

Re-read the thread.  At every point I'm talking about looking for ports
I (and others) might want to maintain, as a service to their users.  Now
ask yourself why I've been getting so much resistance to that, when we
keep hearing how deprecated ports can be easily resurrected if someone
steps up to maintain them?  


Every response from the committers ignored what I said I was trying to
do, and instead repeated the same old arguments about stale,
unfetchable, broken or superceded ports.  That talking points response
tells me that they didn't want me doing what I was doing to buck an
already-established policy of letting unmaintained ports die unless and
until someone complains.

Today wasn't the first time I've had this discussion with them.  But it
was the last straw as far as I'm concerned.

___
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: Dropping maintainership of my ports

[Erik Trulsson]

On Wed, Apr 27, 2011 at 12:15:43AM -0700, Charlie Kester wrote:
 On Tue 26 Apr 2011 at 23:27:40 PDT John Marino wrote:
 
 You're just sulking because your idea of identifying popular ports
 wasn't met with enthusiasm.  
 
 
 No, it's more than that.  I got the distinct impression that many of the
 committers would be unhappy if I took maintainership of some of the
 ports I might identify as popular, because it would interfere with
 their plans to trim the portstree.


Then you have misunderstood things.  I don't think anybody would be
unhappy if you (or anybody else) took maintainership of one or more of
the currently unmaintained ports.
What plans there are, are not so much about trimming the portstree in
general but trimming the number of unmaintained ports.

What is met with uninterest is your plans to identify popular ports.


 Re-read the thread.  At every point I'm talking about looking for ports
 I (and others) might want to maintain, as a service to their users.  Now
 ask yourself why I've been getting so much resistance to that, when we
 keep hearing how deprecated ports can be easily resurrected if someone
 steps up to maintain them?  

Actually you spend much time speaking about/looking for popular ports
and that is what is met with uninterest.
If you want to take maintainership of a port because you personally use
that port and want to have it working, that is great.
If you want to take maintainership of a port because you believe that
it is a popular port, then go ahead, just don't expect much help with
identifying such ports.

 
 Every response from the committers ignored what I said I was trying to
 do, and instead repeated the same old arguments about stale,
 unfetchable, broken or superceded ports.  That talking points response
 tells me that they didn't want me doing what I was doing to buck an
 already-established policy of letting unmaintained ports die unless and
 until someone complains.

(Actually the policy is that unmaintained and non-working ports should
be let to die, unless somebody steps up to fix the port and take
maintainership.)

Nobody is stopping you from assuming maintainership of one or more of
those unmaintained ports, and thus preventing them from being removed.





-- 
Insert your favourite quote here.
Erik Trulsson
ertr1...@student.uu.se
___
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: Dropping maintainership of my ports

[Kurt Jaeger]

Hi!

  No, it's more than that.  I got the distinct impression that many of the
  committers would be unhappy if I took maintainership of some of the
  ports I might identify as popular, because it would interfere with
  their plans to trim the portstree.

 Then you have misunderstood things.  I don't think anybody would be
 unhappy if you (or anybody else) took maintainership of one or more of
 the currently unmaintained ports.

There are two things. Becoming a maintainer seems to be really easy.

Having one's PRs committed is a bit more difficult and sometimes
takes 4-6 weeks (I had a case recently with 155399 and 155400).

Maybe, if maintainer can somehow easily become ports committer,
this hurdle might be lower ?

-- 
p...@opsec.eu+49 171 3101372 9 years to go !
___
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: Dropping maintainership of my ports

[Jerry]

On Wed, 27 Apr 2011 09:49:58 +0200
Erik Trulsson ertr1...@student.uu.se articulated:

 On Wed, Apr 27, 2011 at 12:15:43AM -0700, Charlie Kester wrote:
  On Tue 26 Apr 2011 at 23:27:40 PDT John Marino wrote:
  
  You're just sulking because your idea of identifying popular ports
  wasn't met with enthusiasm.  
  
  
  No, it's more than that.  I got the distinct impression that many
  of the committers would be unhappy if I took maintainership of some
  of the ports I might identify as popular, because it would
  interfere with their plans to trim the portstree.
 
 
 Then you have misunderstood things.  I don't think anybody would be
 unhappy if you (or anybody else) took maintainership of one or more of
 the currently unmaintained ports.
 What plans there are, are not so much about trimming the portstree in
 general but trimming the number of unmaintained ports.
 
 What is met with uninterest is your plans to identify popular ports.
 
 
  Re-read the thread.  At every point I'm talking about looking for
  ports I (and others) might want to maintain, as a service to their
  users.  Now ask yourself why I've been getting so much resistance
  to that, when we keep hearing how deprecated ports can be easily
  resurrected if someone steps up to maintain them?  
 
 Actually you spend much time speaking about/looking for popular
 ports and that is what is met with uninterest.
 If you want to take maintainership of a port because you personally
 use that port and want to have it working, that is great.
 If you want to take maintainership of a port because you believe that
 it is a popular port, then go ahead, just don't expect much help
 with identifying such ports.
 
  
  Every response from the committers ignored what I said I was trying
  to do, and instead repeated the same old arguments about stale,
  unfetchable, broken or superceded ports.  That talking points
  response tells me that they didn't want me doing what I was doing
  to buck an already-established policy of letting unmaintained ports
  die unless and until someone complains.
 
 (Actually the policy is that unmaintained and non-working ports should
 be let to die, unless somebody steps up to fix the port and take
 maintainership.)
 
 Nobody is stopping you from assuming maintainership of one or more of
 those unmaintained ports, and thus preventing them from being removed.

I concur with Erik. I think you are totally missing the point of the
original post. The desired wish was to remove dead ports that could not
be fetched, or would not build. Possibly, even superseded ports;
although that was not specifically mentioned I don't believe. In to
many of those cases those ports have no formal maintainer.
Unfortunately, some do. In any case, it was proposed that those said
ports be removed. Ports that are current would not be affected. As you
stated, your ports are current and in working order. This proposal
would therefore not effect you unless I am also misreading the intent
of the proposal.

-- 
Jerry ✌
jerry+po...@seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
The more we disagree, the more chance
there is that at least one of us is right.
___
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: Dropping maintainership of my ports

[Eitan Adler]

If after this thread you still want to drop maintership I'd like the following:
 deskutils/teapot
 math/ised
 security/ccrypt
 sysutils/moreutils
 sysutils/moreutils-parallel

 I've been told that we shouldn't be looking for reasons to save any
 unmaintained port,

What you have been told is
no-one steps up to (a) fix the problem, (b) take maintainership and
(c) _continue_ with maintainership. Well, in that case, the port does
not _deserve_ to live.  After all, no-one cares about it.  If they
did, they'd take care of (a) thru (c) above.

If you are stepping up to do the work that is great and we thank you
for that! We we don't want is people who only volunteer for part (a)
and don't continue with (b) and (c).

This is because the work for fixing these ports falls on the rest of
the community, and mainly the committers if it were to break again or
when making sweeping changes to the tree. A large amount of the work
that goes into things like a gmake or autotools upgrade is fixing
individual ports that broke. If people step up to continue to maintain
the now deprecated ports I see nothing wrong with helping them to do
so. If that someone is you - even better!

 and I was specifically told this in response to my
 efforts to identify ports that have a lot of users.

Merely finding popular ports does not help. We need people who have
the time and energy to maintain the ports.
I do not want to say that we are a volunteer project and as such are
forgiven  however such a model does change how we must do things. We
can not assign ports to people, even committers, unless they agree
to do the work.

Furthermore we can use maintainership to judge popularity if
indirectly and imperfectly. If no one steps  up to do the work of all
the port's users it is not that popular.

If you are the one stepping up to do the work I would urge you
continue! However merely pointing at the port and saying this needs
to be fixed won't help as someone still has to fix it.

 So I don't think current policy supports the conclusion that we need to find 
 someone to take them soon.

The policy is one of passiveness and this seems to be the main
difference between the others and the you. Correct me if I am wrong
but you believe that we should be trying as hard as we can to find
somehow or someone to save these ports. Others believe that if someone
wants to they can step up and do the work to save these ports.


On Wed, Apr 27, 2011 at 4:23 AM, Kurt Jaeger li...@opsec.eu wrote:
 Then you have misunderstood things.  I don't think anybody would be
 unhappy if you (or anybody else) took maintainership of one or more of
 the currently unmaintained ports.

 There are two things. Becoming a maintainer seems to be really easy.

Becoming a maintainer requires that you commit to do the work to
ensure that a certain program works on FreeBSD. How easy this is
depends on you.

 Having one's PRs committed is a bit more difficult and sometimes
 takes 4-6 weeks (I had a case recently with 155399 and 155400).

There is a lot of work that has to be done in the background even if
no new ports are added. Things like the gmake upgrade and new ports
features take a lot of time.  Furthermore adding a port seems to be a
trivial task, however the committers have to (a) fix it up if it is
formatted badly (b) test it in a tinderbox and only then (c) commit
it. This takes more time than just cvs commit. A lot of work has
been done in recent years to make this process faster and I'm sure
more could be done - but a lot of people don't realize how much work
goes on behind the scenes




-- 
Eitan Adler
___
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: Dropping maintainership of my ports

[Kurt Jaeger]

Eitan Adler wrote:
 On Wed, Apr 27, 2011 at 4:23 AM, Kurt Jaeger li...@opsec.eu wrote:
  Then you have misunderstood things.  I don't think anybody would be
  unhappy if you (or anybody else) took maintainership of one or more of
  the currently unmaintained ports.
 
  There are two things. Becoming a maintainer seems to be really easy.
 
 Becoming a maintainer requires that you commit to do the work to
 ensure that a certain program works on FreeBSD. How easy this is
 depends on you.

Yes, that's how I handle it.

  Having one's PRs committed is a bit more difficult and sometimes
  takes 4-6 weeks (I had a case recently with 155399 and 155400).
 
 There is a lot of work that has to be done in the background even if
 no new ports are added.

I'm aware of this. What I see is that only a few ports committer
do most of the commits of the small leaf ports. This would burn
me out as well, if I had to do it 8-}

So, if the maintainers of the small leaf ports would be able
to commit their work themselves, it would free the ports committers
with the large ports projects on their hands to work on those ?

Would this work ?

 Things like the gmake upgrade and new ports
 features take a lot of time.  Furthermore adding a port seems to be a
 trivial task, however the committers have to (a) fix it up if it is
 formatted badly (b) test it in a tinderbox and only then (c) commit
 it.

I use three boxes (for 8.1 i386, amd64 and 9-current amd64) to
test. I do not use a tinderbox, as I assume considerable complexity
to set one up.

Does using a tinderbox make a large difference ?

 This takes more time than just cvs commit. A lot of work has
 been done in recent years to make this process faster and I'm sure
 more could be done - but a lot of people don't realize how much work
 goes on behind the scenes

I agree, the infrastructure is massive!

-- 
p...@opsec.eu+49 171 3101372 9 years to go !
___
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: Dropping maintainership of my ports

[Eitan Adler]

 So, if the maintainers of the small leaf ports would be able
 to commit their work themselves, it would free the ports committers
 with the large ports projects on their hands to work on those ?

 Would this work ?

If you look through this list's archives I actually proposed this idea
myself once ;-) The problem is that (a) often maintainers don't do the
work 100% well. I am not knocking everyone - but just because you
_say_ you will do the work doesn't mean you _will_ do it. Furthermore
becoming a committer implies a certain level of trust beyond just you
can submit patches as you get shell access to the FreeBSD machines
and other such things.


 I use three boxes (for 8.1 i386, amd64 and 9-current amd64) to
 test. I do not use a tinderbox, as I assume considerable complexity
 to set one up.

You may want to mention that you use said three machines in the PR -
it would be of service. Different committers have differing policies
for what they will commit. Some will accept that, others will want
tinderbox logs, and others will always test every patch themselves.


 Does using a tinderbox make a large difference ?
Using a tinderbox ensures that a clean build works (ie that there
are no missing dependencies).

 I agree, the infrastructure is massive!

23,000 ports held together with Makefiles - I'm still surprised it works ;)

-- 
Eitan Adler
___
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: Dropping maintainership of my ports

[Diane Bruce]

On Wed, Apr 27, 2011 at 07:35:58AM -0400, Jerry wrote:
 On Wed, 27 Apr 2011 09:49:58 +0200
 Erik Trulsson ertr1...@student.uu.se articulated:
 
  On Wed, Apr 27, 2011 at 12:15:43AM -0700, Charlie Kester wrote:
   On Tue 26 Apr 2011 at 23:27:40 PDT John Marino wrote:
   
...
   
   Every response from the committers ignored what I said I was trying
   to do, and instead repeated the same old arguments about stale,
   unfetchable, broken or superceded ports.  That talking points

No, no and no. If you have a copy of the upstream package the port was
based upon and it is open source, you can 'fork' it. Create a project
on sourceforge, or Berlioz, or somewhere, put the package there, announce it
get some people together to maintain it. That has the advantage of having
FreeBSD minded people maintaing it upstream. That's all. Easy Peasy.
That's for unfetchable ports or even superceded ports. If you prefer
an older program than a supposed newer suggested replacement, you can
fork the older program. That's how it works.

  (Actually the policy is that unmaintained and non-working ports should
  be let to die, unless somebody steps up to fix the port and take
  maintainership.)

Exactly. 

  
  Nobody is stopping you from assuming maintainership of one or more of
  those unmaintained ports, and thus preventing them from being removed.
 
 I concur with Erik. I think you are totally missing the point of the
 original post. The desired wish was to remove dead ports that could not
 be fetched, or would not build. Possibly, even superseded ports;

Right.

- Diane
-- 
- d...@freebsd.org d...@db.net http://www.db.net/~db
  Why leave money to our children if we don't leave them the Earth?
___
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: Dropping maintainership of my ports

[Michel Talon]

Eitan Adler wrote:

 There is a lot of work that has to be done in the background even if
 no new ports are added. Things like the gmake upgrade and new ports
 features take a lot of time.  Furthermore adding a port seems to be a
 trivial task, however the committers have to (a) fix it up if it is
 formatted badly (b) test it in a tinderbox and only then (c) commit
 it. This takes more time than just cvs commit. A lot of work has
 been done in recent years to make this process faster and I'm sure
 more could be done - but a lot of people don't realize how much work
 goes on behind the scenes

I think it is important to clean up ports because otherwise there is a
big burden on the FreeBSD organization, and also on each individual
user, when they upgrade their machine. I think on the other hand that
some ports are especially important, and don't always receive the care
they need, for reasons that i don't know. I have taken some time to look
at some ports in the lang category that are unmaintained or are
severely old.

I have noted that eiffel 13a is deprecated and has an expiration date.
Indeed i have found old copies of this software, and it seems that the
people doing it have disappeared someway. However at least one is now
listed as contributor to gobo-eiffel
http://sourceforge.net/projects/gobo-eiffel/
which is not a freebsd port.
There is the official eiffelstudio port, which has a valid download
link but no maintainer, and smarteiffel which is maintained.

I am more interested by the cmucl lisp compiler. In the ports we can
find cmucl 19f which is maintained by Martin Cracauer, but is already
quite old, and there is no maintainer for cmucl-extras. In fact the
cmucl project does the work of providing precompiled stuff for various
architectures (the lisp compiler is written in lisp so can only be
compiled by a recent enough precompiled compiler, anyways) and in
particular one finds freebsd binaries here:
http://common-lisp.net/project/cmucl/downloads/snapshots/2011/04/
These binaries are compiled on freebsd_8.1, and there are two versions
the unicode version and the non-unicode version, plus the cmucl-extra
(localized messages, an adapted editor, called hemlock plus some
goodies). 

So my point is, how is it that cmucl freebsd version finds care and love
in the cmucl community, but that this does not extend to an adequate 
place in the freebsd ports? 

The other big lisp from the same ancestry, sbcl is better maintained,
since the last version is 1.0.47, while freebsd is at 1.0.43, that is 6
months old. These lisps are *very* important for their use in the CAS
software maxima, which is actively developed and used by a lot of people
(in ancient times the traditional compiler for maxima was gcl but it
seems it doesn't work well nowadays, and clisp is far too slow). But
they are also important for many other uses, and at this point i see an
important omission in the ports system. The standard way nowadys to
install lisp packages is to use quicklisp
http://www.quicklisp.org/beta/
and after that hundreds of applications can be installed automatically
in the same way as cpan does for perl modules. Instead there are a
select few lisp applications in the ports, which have a clisp and a sbcl
slave port. This is strange.


-- 

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: Dropping maintainership of my ports

[Chris Rees]

On 27 April 2011 13:54, Kurt Jaeger li...@opsec.eu wrote:
 Eitan Adler wrote:
 Things like the gmake upgrade and new ports
 features take a lot of time.  Furthermore adding a port seems to be a
 trivial task, however the committers have to (a) fix it up if it is
 formatted badly (b) test it in a tinderbox and only then (c) commit
 it.

 I use three boxes (for 8.1 i386, amd64 and 9-current amd64) to
 test. I do not use a tinderbox, as I assume considerable complexity
 to set one up.

Nah, have a look at [1]. Easy as pie.

 Does using a tinderbox make a large difference ?

Yes! It finds hiccups in pkg-plist (very difficult to notice
manually), it tests in different versions -- just add them to the
queue.

If you'd really like to try it out, I'll give you an account on my
machine. Let me know.

Chris


[1] http://tinderbox.marcuscom.com/README/
___
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

Dropping maintainership of my ports

[Charlie Kester]

Well, due to some serious philosophical differences re these
deprecation campaigns and what seems to be resistance to any further
discussion, I don't think I can continue working with the committers.
So I'm stepping down.

If no one else wants to maintain them, please reset the maintainer of 
the following ports to po...@freebsd.org:


audio/mcplay
deskutils/osmo
deskutils/teapot
devel/argtable
devel/egypt
devel/gengetopt
devel/libXGP
devel/libYGP
finance/xinvest
finance/xquote
graphics/box
graphics/boxer
graphics/fly
graphics/sng
math/ised
misc/vifm
misc/xsw
multimedia/gpodder
multimedia/openshot
multimedia/photofilmstrip
security/beecrypt
security/ccrypt
security/nettle
security/ranpwd
sysutils/dircomp
sysutils/gaffitter
sysutils/iextract
sysutils/lookat
sysutils/moreutils
sysutils/moreutils-parallel
sysutils/ncdu
sysutils/rdup
textproc/tdhkit
x11/fbpanel


___
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: Dropping maintainership of my ports

[Ruslan Mahmatkhanov]

27.04.2011 05:43, Charlie Kester пишет:


Well, due to some serious philosophical differences re these
deprecation campaigns and what seems to be resistance to any further
discussion, I don't think I can continue working with the committers.
So I'm stepping down.

If no one else wants to maintain them, please reset the maintainer of the
following ports to po...@freebsd.org:



I'm interesting in maintaing of this ports:


multimedia/gpodder
sysutils/rdup


--
Regards,
Ruslan
___
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: Dropping maintainership of my ports

[Zhihao Yuan]

On Tue, Apr 26, 2011 at 8:43 PM, Charlie Kester corky1...@comcast.net wrote:

 Well, due to some serious philosophical differences re these
 deprecation campaigns and what seems to be resistance to any further
 discussion, I don't think I can continue working with the committers.
 So I'm stepping down.

 If no one else wants to maintain them, please reset the maintainer of the
 following ports to po...@freebsd.org:

 audio/mcplay
 deskutils/osmo
 deskutils/teapot
 devel/argtable
 devel/egypt
 devel/gengetopt
 devel/libXGP
 devel/libYGP
 finance/xinvest
 finance/xquote
 graphics/box
 graphics/boxer
 graphics/fly
 graphics/sng
 math/ised
 misc/vifm
 misc/xsw
 multimedia/gpodder
 multimedia/openshot
 multimedia/photofilmstrip
 security/beecrypt
 security/ccrypt
 security/nettle
 security/ranpwd
 sysutils/dircomp
 sysutils/gaffitter
 sysutils/iextract
 sysutils/lookat
 sysutils/moreutils
 sysutils/moreutils-parallel
 sysutils/ncdu
 sysutils/rdup
 textproc/tdhkit
 x11/fbpanel

O-o-ok... philosophical differences.

audio/mcplay and the 3 multimedia-related ports, + fbpanel, have many
users, AFAIK, and require much works. We need to someone to take them
soon.



 ___
 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




-- 
Zhihao Yuan
The best way to predict the future is to invent it.
___
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: Should I be adding LICENSE info to my ports?

[Emanuel Haupt]

Sahil Tandon sa...@freebsd.org wrote:
 On Tue, 2011-01-25 at 16:17:29 -0800, Charlie Kester wrote:
 
  Today on FreshPorts I see some bulk commits adding LICENSE info to
  40+ ports. And I've noticed LICENSE being added in many other recent
  commits.
 
 Right, ehaupt@ updated several of his ports to include LICENSE.

I was very reluctant to do so but now that the license framework has
been around for some time I thought I give it a go.

As Sahil pointed out it's entirely up to you. Better have no license
specified if you're not sure about it. You can not always trust the
included COPYING file. There are many cases where a port comes with
several different licenses. I found that cross checking with different
linux distros could often bring some clarification.

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

Re: Should I be adding LICENSE info to my ports?

[Charlie Kester]

On Wed 26 Jan 2011 at 01:13:50 PST Emanuel Haupt wrote:

Sahil Tandon sa...@freebsd.org wrote:

On Tue, 2011-01-25 at 16:17:29 -0800, Charlie Kester wrote:

 Today on FreshPorts I see some bulk commits adding LICENSE info to
 40+ ports. And I've noticed LICENSE being added in many other recent
 commits.

Right, ehaupt@ updated several of his ports to include LICENSE.


I was very reluctant to do so but now that the license framework has
been around for some time I thought I give it a go.

As Sahil pointed out it's entirely up to you. Better have no license
specified if you're not sure about it. You can not always trust the
included COPYING file. There are many cases where a port comes with
several different licenses. I found that cross checking with different
linux distros could often bring some clarification.


Good tips, thanks.  There's also often some licensing info in the
author's manpage, website, or other documentation.

I'm not going to submit a flurry of PR's to add this to all my ports,
but I will begin gathering the info so I can include it as part of any
other updates.
___
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

Should I be adding LICENSE info to my ports?

[Charlie Kester]

Today on FreshPorts I see some bulk commits adding LICENSE info to 40+
ports. And I've noticed LICENSE being added in many other recent commits.

But I still don't see anything in the Porter's Handbook about how
maintainers should use this infrastructure in their ports.  


I thought we were waiting on the Handbook, but it seems a lot of people
are proceeding without it.  Should I do likewise?  


(There are now enough examples out there that I *think* I can figure
what to do...)

___
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: Should I be adding LICENSE info to my ports?

[Sahil Tandon]

On Tue, 2011-01-25 at 16:17:29 -0800, Charlie Kester wrote:

 Today on FreshPorts I see some bulk commits adding LICENSE info to 40+
 ports. And I've noticed LICENSE being added in many other recent
 commits.

Right, ehaupt@ updated several of his ports to include LICENSE.

 But I still don't see anything in the Porter's Handbook about how
 maintainers should use this infrastructure in their ports.  I thought
 we were waiting on the Handbook, but it seems a lot of people are
 proceeding without it.  Should I do likewise?

It's entirely up to you; no requirement.

 (There are now enough examples out there that I *think* I can figure
 what to do...)

Also be sure to review bsd.licenses.mk.

-- 
Sahil Tandon sa...@freebsd.org
___
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: Should I be adding LICENSE info to my ports?

[Charlie Kester]

On Tue 25 Jan 2011 at 19:46:36 PST Sahil Tandon wrote:


It's entirely up to you; no requirement.


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

Dropping maintainership of my ports

[Tobias Roth]

Hi

I haven't been using FreeBSD as a desktop for a while now, and am thus
dropping maintainerships of my ports. If anyone wants to step up and
take over maintainership, please send me an email. For everything left
over, I will send PRs to reset the maintainer to ports@ in about two weeks.

The ports are

audio/py-eyed3 : Python module for processing ID3 tags
devel/py-testoob : An advanced unit testing framework for PyUnit
x11/fbpanel : Desktop panel with taskbar, pager, launchbar and more
deskutils/gkrellm-gtodo : GKrellM2 plugin to tracks tasks and to-dos
deskutils/gkrellm-reminder2 : GKrellM2 plugin that reminds you of events
deskutils/gkrellm-timers : GKrellM2 plugin for the setting of countdowns
misc/gkx86info2 : GKrellM2 plugin that prints the current clock speed
net-p2p/gkrellm-gift : GKrellM2 plugin that monitors giFT transfers
net/gkrellmmultiping2 : GKrellM2 multiping plugin
sysutils/gkrellm-trayicons : GKrellM2 plugin to display definable icons
as notifiers or launchers

deskutils/treeline : maintainership already taken by Pawel Pekala, thanks!

Thanks in advance,
Tobias
___
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: Dropping maintainership of my ports

[Ruslan Mahmatkhanov]

27.09.2010 23:32, Tobias Roth пишет:

Hi

I haven't been using FreeBSD as a desktop for a while now, and am thus
dropping maintainerships of my ports. If anyone wants to step up and
take over maintainership, please send me an email. For everything left
over, I will send PRs to reset the maintainer to ports@ in about two weeks.

The ports are

audio/py-eyed3 : Python module for processing ID3 tags


I want this one


devel/py-testoob : An advanced unit testing framework for PyUnit
x11/fbpanel : Desktop panel with taskbar, pager, launchbar and more
deskutils/gkrellm-gtodo : GKrellM2 plugin to tracks tasks and to-dos
deskutils/gkrellm-reminder2 : GKrellM2 plugin that reminds you of events
deskutils/gkrellm-timers : GKrellM2 plugin for the setting of countdowns
misc/gkx86info2 : GKrellM2 plugin that prints the current clock speed
net-p2p/gkrellm-gift : GKrellM2 plugin that monitors giFT transfers
net/gkrellmmultiping2 : GKrellM2 multiping plugin
sysutils/gkrellm-trayicons : GKrellM2 plugin to display definable icons
as notifiers or launchers

deskutils/treeline : maintainership already taken by Pawel Pekala, thanks!

Thanks in advance,
Tobias
___
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




--
Regards,
Ruslan
___
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: Dropping maintainership of my ports

[Steven Kreuzer]

On Sep 27, 2010, at 4:23 PM, Ruslan Mahmatkhanov wrote:

 27.09.2010 23:32, Tobias Roth пишет:
 Hi
 
 I haven't been using FreeBSD as a desktop for a while now, and am thus
 dropping maintainerships of my ports. If anyone wants to step up and
 take over maintainership, please send me an email. For everything left
 over, I will send PRs to reset the maintainer to ports@ in about two weeks.
 
 The ports are
 
 audio/py-eyed3 : Python module for processing ID3 tags

 I want this one

Updated MAINTAINER to cvs-...@yandex.ru

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

Re: Dropping maintainership of my ports

[Charlie Kester]

On Mon 27 Sep 2010 at 12:32:56 PDT Tobias Roth wrote:

x11/fbpanel : Desktop panel with taskbar, pager, launchbar and more


I use this and can take maintainership.
___
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: Dropping maintainership of my ports

[Steven Kreuzer]

On Sep 27, 2010, at 7:36 PM, Charlie Kester wrote:

 On Mon 27 Sep 2010 at 12:32:56 PDT Tobias Roth wrote:
 x11/fbpanel : Desktop panel with taskbar, pager, launchbar and more
 
 I use this and can take maintainership.

You have been set as the maintainer.

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

Re: Dropping maintainership of my ports

[Tobias Roth]

On 9/28/10 2:34 AM, Steven Kreuzer wrote:
 On Sep 27, 2010, at 7:36 PM, Charlie Kester wrote:
 
 On Mon 27 Sep 2010 at 12:32:56 PDT Tobias Roth wrote:
 x11/fbpanel : Desktop panel with taskbar, pager, launchbar and more

 I use this and can take maintainership.
 
 You have been set as the maintainer.

Thanks Ruslan, Charlie and Steven!
___
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

Stepping down from my ports

[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: Stepping down from my ports

[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: Stepping down from my ports

[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 sa...@freebsd.org
___
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: My ports.

[Pietro Cerutti]

On 2010-Feb-22, 08:48, Marcelo Araujo wrote:
 Hi guys,
 
 There are some ports that I haven't interested and neither used anymore,
 so I'm here to check if there is anyone that would be interested to push
 them and maintain those updated before set up those to po...@.
 
 Please, send me a list of ports that you want and I'm gonna release to you
 or fell free to take it by yourself.


I'll take these.

x11-toolkits/fox12
x11-toolkits/fox14
x11-toolkits/fox16

-- 
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org

PGP Public Key:
http://gahr.ch/pgp


pgpkUTqc9JvKH.pgp
Description: PGP signature

Re: My ports.

[Marcelo]

Hi dear Pietro,

Which one do you intend to catch it up in your hands?
Fell free and go ahead!


Best Regards,


2010/3/11 Pietro Cerutti g...@gahr.ch

 On 2010-Feb-22, 08:48, Marcelo Araujo wrote:
  Hi guys,
 
  There are some ports that I haven't interested and neither used anymore,
  so I'm here to check if there is anyone that would be interested to push
  them and maintain those updated before set up those to po...@.
 
  Please, send me a list of ports that you want and I'm gonna release to
 you
  or fell free to take it by yourself.
 

 I'll take these.

 x11-toolkits/fox12
 x11-toolkits/fox14
 x11-toolkits/fox16

 --
 Pietro Cerutti
 The FreeBSD Project
 g...@freebsd.org

 PGP Public Key:
 http://gahr.ch/pgp




-- 
Marcelo Araujo
ara...@freebsd.org
___
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: My ports.

[Pietro Cerutti]

On 2010-Mar-11, 15:00, Marcelo wrote:
 Hi dear Pietro,

Hi Marcelo,

 Which one do you intend to catch it up in your hands?

  I'll take these.
 
  x11-toolkits/fox12
  x11-toolkits/fox14
  x11-toolkits/fox16

Uhm, eh?

-- 
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org

PGP Public Key:
http://gahr.ch/pgp


pgpQxGWFoHgdu.pgp
Description: PGP signature

Re: My ports.

[Marcelo]

Please, go ahead, they need an update urgently.
Thanks to care on they.


2010/3/11 Pietro Cerutti g...@gahr.ch

 On 2010-Mar-11, 15:00, Marcelo wrote:
  Hi dear Pietro,

 Hi Marcelo,

  Which one do you intend to catch it up in your hands?

   I'll take these.
  
   x11-toolkits/fox12
   x11-toolkits/fox14
   x11-toolkits/fox16

 Uhm, eh?

 --
 Pietro Cerutti
 The FreeBSD Project
 g...@freebsd.org

 PGP Public Key:
 http://gahr.ch/pgp




-- 
Marcelo Araujo
ara...@freebsd.org
___
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: My ports.

[Pietro Cerutti]

On 2010-Mar-11, 15:59, Marcelo wrote:
 Please, go ahead, they need an update urgently.
 Thanks to care on they.

Actually, I'm thinking about dropping support for fox12 :)

I'll DEPRECATE it and remove it in a few weeks. In the process, I'll
drop x11-toolkits/fxscintilla-fox12, x11-toolkits/ruby-fox12, and I'll
update editors/mondrian to use fox16. That should happen seemingly
painlessly :)

 
 
 2010/3/11 Pietro Cerutti g...@gahr.ch
 
  On 2010-Mar-11, 15:00, Marcelo wrote:
   Hi dear Pietro,
 
  Hi Marcelo,
 
   Which one do you intend to catch it up in your hands?
 
I'll take these.
   
x11-toolkits/fox12
x11-toolkits/fox14
x11-toolkits/fox16
 
  Uhm, eh?
 
  --
  Pietro Cerutti
  The FreeBSD Project
  g...@freebsd.org
 
  PGP Public Key:
  http://gahr.ch/pgp
 
 
 
 
 -- 
 Marcelo Araujo
 ara...@freebsd.org

-- 
Pietro Cerutti
The FreeBSD Project
g...@freebsd.org

PGP Public Key:
http://gahr.ch/pgp


pgpHsd4tSp3k8.pgp
Description: PGP signature

Re: My ports.

[Marcelo]

You are right, it is the best way. I supposed to have done it  a couple of
months ago, but unfortunately my free time isn't enough, right now.

Thanks again.

2010/3/11 Pietro Cerutti g...@gahr.ch

 On 2010-Mar-11, 15:59, Marcelo wrote:
  Please, go ahead, they need an update urgently.
  Thanks to care on they.

 Actually, I'm thinking about dropping support for fox12 :)

 I'll DEPRECATE it and remove it in a few weeks. In the process, I'll
 drop x11-toolkits/fxscintilla-fox12, x11-toolkits/ruby-fox12, and I'll
 update editors/mondrian to use fox16. That should happen seemingly
 painlessly :)

 
 
  2010/3/11 Pietro Cerutti g...@gahr.ch
 
   On 2010-Mar-11, 15:00, Marcelo wrote:
Hi dear Pietro,
  
   Hi Marcelo,
  
Which one do you intend to catch it up in your hands?
  
 I'll take these.

 x11-toolkits/fox12
 x11-toolkits/fox14
 x11-toolkits/fox16
  
   Uhm, eh?
  
   --
   Pietro Cerutti
   The FreeBSD Project
   g...@freebsd.org
  
   PGP Public Key:
   http://gahr.ch/pgp
  
 
 
 
  --
  Marcelo Araujo
  ara...@freebsd.org

 --
 Pietro Cerutti
 The FreeBSD Project
 g...@freebsd.org

 PGP Public Key:
 http://gahr.ch/pgp




-- 
Marcelo Araujo
ara...@freebsd.org
___
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: My ports.

[Marcelo]

Hi dear Eitan,

It was done.

Thanks.


2010/3/3 Marcelo araujobsdp...@gmail.com

 Hi dear,

 Tomorrow I'll pass these to you...

 Thanks.

 2010/2/28 Eitan Adler eitanadlerl...@gmail.com

 I'll take these:

  sysutils/googlog
  textproc/align
  x11/xbindkeys




 --
 Marcelo Araujo
 ara...@freebsd.org




-- 
Marcelo Araujo
ara...@freebsd.org
___
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: My ports.

[Marcelo]

Hi dear,

Tomorrow I'll pass these to you...

Thanks.

2010/2/28 Eitan Adler eitanadlerl...@gmail.com

 I'll take these:

  sysutils/googlog
  textproc/align
  x11/xbindkeys




-- 
Marcelo Araujo
ara...@freebsd.org
___
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: My ports.

[Eitan Adler]

I'll take these:

 sysutils/googlog
 textproc/align
 x11/xbindkeys
___
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

My ports.

[Marcelo Araujo]

Hi guys,

There are some ports that I haven't interested and neither used anymore,
so I'm here to check if there is anyone that would be interested to push
them and maintain those updated before set up those to po...@.

Please, send me a list of ports that you want and I'm gonna release to you
or fell free to take it by yourself.

Follow bellow those ports that I haven't interest anymore.

audio/festlex-ogi
audio/napster
cad/impact
devel/c4
devel/inilib
devel/libol
devel/nx
devel/pmk
devel/ruby-date2
devel/cx_Freeze
graphics/libqglviewer
graphics/mesa-demos
graphics/py-freeimagepy
java/jcalendar
lang/execline
lang/sisc
mail/ask
mail/exipick
mail/gotmail
mail/prom-wl
mail/pronto
math/cln
math/gdcalc
math/ruby-algebra
net/c3270
net/dgd-net
net/gnet
net/hf6to4
net/lft
net/java-beepcore
net/jcifs
net/mars_nwe
net/p5-Net-Analysis
net/passlogd
net/pygopherd
net/redir
net-mgmt/ipfm
print/gl2ps
print/libotf
print/mup
security/gss
security/krb4
security/libwhisker
security/shishi
security/tlswrap
sysutils/googlog
textproc/align
textproc/doclifter
textproc/ruby-xmlconfigfile
www/asterisk-fop
www/bins
www/netoffice
x11/xbindkeys
x11-clocks/sanduhr
x11-toolkits/fox12
x11-toolkits/fox14
x11-toolkits/fox16
x11-toolkits/fxscintilla
x11-toolkits/ruby-fox12
x11-toolkits/viewklass

Best Regards,
-- 
Marcelo Araujo
ara...@freebsd.org
http://www.FreeBSD.org
A carelessly planned project will take three times
longer than expected; a carefully planned project will
take only twice as long.


pgpqG08Rc50wE.pgp
Description: PGP signature

Re: My ports.

[Robert Noland]

On Mon, 2010-02-22 at 08:48 -0300, Marcelo Araujo wrote:
 graphics/mesa-demos

Please sweep this under x11@ like the other mesa related ports.

robert.

-- 
Robert Noland rnol...@freebsd.org
FreeBSD

___
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: My ports.

[Alex Dupre]

Marcelo Araujo ha scritto:
 net/jcifs

I can take this one.

-- 
Alex Dupre
___
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: My ports.

[Stephen Montgomery-Smith]

Marcelo Araujo wrote:

Hi guys,

There are some ports that I haven't interested and neither used anymore,
so I'm here to check if there is anyone that would be interested to push
them and maintain those updated before set up those to po...@.

Please, send me a list of ports that you want and I'm gonna release to you
or fell free to take it by yourself.

Follow bellow those ports that I haven't interest anymore.



math/cln


I'll take this one if no-one else wants it.

___
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