[Patch] Ports and rsync

2012-09-16 Thread CyberLeo Kitsana
I've submitted ports/171681[1] with a patch to add rsync to the list of
update methods for the ports tree. Hopefully I'm not the only one who
desires such functionality.

References:
[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171681

-- 
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net


Furry Peace! - http://.fur.com/peace/
___
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"


sysutils/bacula2-client and sysutils/bacula2-server

2012-09-16 Thread Václav Zeman
Hi.

I am no longer interested in maintaining sysutils/bacula2-client and
sysutils/bacula2-server ports. I have lost the machine that was using
it. If anybody still needs those, feel free to take over.

(Also the maintainer email noted for the two packes is currently broken.)

-- 
VZ




signature.asc
Description: OpenPGP digital signature


Re: [Patch] Ports and rsync

2012-09-16 Thread Jeffrey Bouquet


--- On Sun, 9/16/12, CyberLeo Kitsana  wrote:

> From: CyberLeo Kitsana 
> Subject: [Patch] Ports and rsync
> To: "FreeBSD Ports" 
> Date: Sunday, September 16, 2012, 3:42 AM
> I've submitted ports/171681[1] with a
> patch to add rsync to the list of
> update methods for the ports tree. Hopefully I'm not the
> only one who
> desires such functionality.
> 
> References:
> [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171681
> 
> -- 
> Fuzzy love,
> -CyberLeo
> Technical Administrator
> CyberLeo.Net Webhosting
> http://www.CyberLeo.Net
> 
> 
> Furry Peace! - http://.fur.com/peace/
> ___
> 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"
> 
Could this substitute for .svn for those who now use csup? Or is
it maybe specific to a local network and nothing upstream. Not
clear the implications, here, or entire scenario of this rsync
methodology (I use it readily for a whole bunch of other stuff.)
 But
I look forward to its implementation... if it occurs.

J. Bouquet
___
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: sysutils/bacula2-client and sysutils/bacula2-server

2012-09-16 Thread Ruslan Mahmatkhanov

Hi,

Václav Zeman wrote on 16.09.2012 22:12:

Hi.

I am no longer interested in maintaining sysutils/bacula2-client and
sysutils/bacula2-server ports. I have lost the machine that was using
it. If anybody still needs those, feel free to take over.

(Also the maintainer email noted for the two packes is currently broken.)


I'll do this. I'd also prefer to deprecate and retire it from the ports 
tree, since it's no longer supported upstream. What do you think?


--
Regards,
Ruslan

Tinderboxing kills... the drives.
___
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: [Patch] Ports and rsync

2012-09-16 Thread CyberLeo Kitsana
On 09/16/2012 01:47 PM, Jeffrey Bouquet wrote:
> On 09/16/12 03:42 AM CyberLeo Kitsana wrote:
>> I've submitted ports/171681[1] with a
>> patch to add rsync to the list of
>> update methods for the ports tree. Hopefully I'm not the
>> only one who
>> desires such functionality.
>>
>> References:
>> [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171681
>
> Could this substitute for .svn for those who now use csup? Or is
> it maybe specific to a local network and nothing upstream. Not
> clear the implications, here, or entire scenario of this rsync
> methodology (I use it readily for a whole bunch of other stuff.)
>  But
> I look forward to its implementation... if it occurs.

To my knowledge, the FreeBSD foundation does not offer rsync services
for ports, though nothing stops anyone from actually doing so; I run one
of my own, updated via portsnap, with a custom overlay for ports that
haven't much usefulness outside of my domain. It seems the easiest
approach, without having to learn the intricacies of creating and
maintaining custom portsnap hosts or trying to set up and feed a
subversion server to host my changes.

This patch just offers an easy way to invoke rsync via 'make update'
without having to dig out the magical rsync invocation flags every time.

-- 
Fuzzy love,
-CyberLeo
Technical Administrator
CyberLeo.Net Webhosting
http://www.CyberLeo.Net


Furry Peace! - http://.fur.com/peace/
___
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"


Status of ports/169660

2012-09-16 Thread Helmut Schneider
Hi,

ports/169660 is waiting for the maintainer for more than 2 months, any
update here?

Thanks, Helmut

___
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: Status of ports/169660

2012-09-16 Thread Radim Kolar

Dne 16.9.2012 22:54, Helmut Schneider napsal(a):

Hi,

ports/169660 is waiting for the maintainer for more than 2 months, any
update here?
if port maintainer is freebsd committer then if it is not committed 
shortly, then usual wait time is about 1 year (or some similar time) 
because its not committed after standard timeout period.


i have similar ports/167289, just about 6 months old, patiently waiting 
for end of itetcu hibernation cycle.


Best solution is to fork freebsd port tree, don't worry its simple.
___
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: Status of ports/169660

2012-09-16 Thread Eitan Adler
On 16 September 2012 19:20, Radim Kolar  wrote:
> Dne 16.9.2012 22:54, Helmut Schneider napsal(a):
>
>> Hi,
>>
>> ports/169660 is waiting for the maintainer for more than 2 months, any
>> update here?

gabor is active. lets see what he has to say.


> if port maintainer is freebsd committer then if it is not committed shortly,
> then usual wait time is about 1 year (or some similar time) because its not
> committed after standard timeout period.

It could be. However people don't always look for them. A *polite*
email to this list is helpful.





-- 
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"