Re: Committing New Ports on Bugzilla

[Neel Chauhan]

Thanks!

-Neel

On 2021-01-01 02:07, Kurt Jaeger wrote:

Hi!


 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252314
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252226
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252224
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252223
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252185
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252151
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252152
 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252150

Could one of you please commit these New Ports?


Done.

___
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: Committing New Ports on Bugzilla

[Kurt Jaeger]

Hi!

>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252314
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252226
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252224
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252223
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252185
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252151
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252152
>  * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252150
> 
> Could one of you please commit these New Ports?

Done.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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"

Committing New Ports on Bugzilla

[Neel Chauhan]

Hi freebsd-ports@,

I hope you all had a great holiday season.

I have a couple of New Ports which I would like someone to commit.

The Ports are:

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252314

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252226

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252224

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252223

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252185

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252151

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252152

 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252150

Could one of you please commit these New Ports?

Have a happy new year!

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

[Bob Eager]

On Sat, 13 Jun 2020 22:54:16 +0200
Kurt Jaeger  wrote:

> Hi!
> 
> > OK, thanks for the advice. Here are two of mine, submitted a little
> > while ago, but still with 'new' status.
> > 
> >  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246237
> > 
> >  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246238
> > 
> > They are two new SIMH emulators, for HP machines.  
> 
> Committed, thanks!
> 

Great, I'll finish off the new version of SIMH itself now!
___
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: New ports...

[Kurt Jaeger]

Hi!

> OK, thanks for the advice. Here are two of mine, submitted a little
> while ago, but still with 'new' status.
> 
>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246237
> 
>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246238
> 
> They are two new SIMH emulators, for HP machines.

Committed, thanks!

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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: New ports...

[Bob Eager]

On Fri, 12 Jun 2020 22:11:52 +0200
Kurt Jaeger  wrote:

> > I've submitted a couple of new ports (to bugs.freebsd.org and I'm
> > curious if one is supposed to do something else after doing that?   
> 
> In general: no. It's helpful to mention those ports here on the list,
> because ports committers are swamped with requests.

OK, thanks for the advice. Here are two of mine, submitted a little
while ago, but still with 'new' status.

 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246237

 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246238

They are two new SIMH emulators, for HP machines.
___
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: New ports...

[Kurt Jaeger]

Hi!

> I've submitted a couple of new ports (to bugs.freebsd.org and I'm
> curious if one is supposed to do something else after doing that? 

In general: no. It's helpful to mention those ports here on the list,
because ports committers are swamped with requests.

> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247211

This one needs fixes so that portlint does no longer complain.

> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246876

This had small issues with missing PLIST_FILES. Fixed, committed!

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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"

New ports...

[Peter Eriksson]

I’ve submitted a couple of new ports (to bugs.freebsd.org 
<http://bugs.freebsd.org/>) and I’m curious if one is supposed to do something 
else after doing that? 

I’ve read and tried following the FreeBSD Porter’s Handbook but that seems to 
“end” after one has submitted it as a diff via the bugzilla system. Looking at 
the (not small) number of new/open entries there I can easily see that new 
stuff might get lost (and/or the committers mitt be swamped :-) so perhaps 
there is some other way one should act?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247211 
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247211>

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246876 
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246876>

- Peter 

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

D22521: new ports: Nvidia headless/hybrid graphics ("Optimus" support) needs commit / review

[Theron Tarigo]

Hello all,

The work by myself and other users of Nvidia-gfx laptops to patch the 
driver to work for us has been stuck in review for a few months now.  
The reason for review of what would normally be a routine new-ports bug 
submission is that changes to x11/nvidia-driver/Makefile are needed to 
avoid redundancy in the new ports.  The maintainer, danfe@ has indicated 
to me that he needed more time to review, but I've asked for an 
indication of a timeframe and haven't heard back for over two weeks.  I 
don't know whether maintainer-timeout is relevant here since the changes 
to x11/nvidia-driver/Makefile are nonfunctional with respect to that 
port; all that happens is to make it behave correctly as a master for 
the new slave port.


Could a ports committer please look into this?

https://reviews.freebsd.org/D22521

Hope danfe@ is well.
Thanks.
Theron
___
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: New Ports Wildfly14, 13 and 12

[Simeo Reig]

I've seen all have been committed, many many  thanks for your help Kurt
Jaeger

My best regards

Simeó Reig
___
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: New Ports Wildfly14, 13 and 12

[Kurt Jaeger]

Hi!

> Port 12 and 13 was made based on a diff from existing port 11 made by 
> Yerenkow.
> Port 14 it's a shar, not a diff because I made it as a new completely port.
> 
> Should I do a shar file for 12 and 13 versions?

I'm testbuilding 12 now. If all works out, I'll go on to wf13.
I'll get back to you if I need anything 8-}

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
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: New Ports Wildfly14, 13 and 12

[Simeo Reig]

>Hi!
>
>>* I have ported Wildfly12, Wildfly13 and Wildfly14 to freeBSD, based on ports
*>>* of former versions ported by yerenkow.
*>
>Thanks!

you are very welcome, my little contribution to freebsd.


>>* PRs are:
*>> >>* https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231119

*>
>Strange packaging for a patch, the tar was not really necessary,
>was it 8-) ?

You are right, It doesn't make to much sense to tar.gz a little diff file.


>
>Is this diff the result of a
>
>svn copy wildfly11 wildfly12
>
>with the matching modifications ?
>
>[...]
>>* Those are my first FreeBSD ports, so if someone can take a look and give
*>>* comments or commit them if they are OK it should be great.
*>
>If you provide a diff from a svn copy, it makes the work for
>the committer much easier to apply the patch and test it.
>
>Are the other patches similar ?


Port 12 and 13 was made based on a diff from existing port 11 made by Yerenkow.
Port 14 it's a shar, not a diff because I made it as a new completely port.

Should I do a shar file for 12 and 13 versions?


Many thanks for your help
___
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: New Ports Wildfly14, 13 and 12

[Kurt Jaeger]

Hi!

> I have ported Wildfly12, Wildfly13 and Wildfly14 to freeBSD, based on ports
> of former versions ported by yerenkow.

Thanks!

> PRs are:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231119

Strange packaging for a patch, the tar was not really necessary,
was it 8-) ?

Is this diff the result of a

svn copy wildfly11 wildfly12

with the matching modifications ?

[...]
> Those are my first FreeBSD ports, so if someone can take a look and give
> comments or commit them if they are OK it should be great.

If you provide a diff from a svn copy, it makes the work for
the committer much easier to apply the patch and test it.

Are the other patches similar ?

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
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"

New Ports Wildfly14, 13 and 12

[Simeo Reig]

Hi all

I have ported Wildfly12, Wildfly13 and Wildfly14 to freeBSD, based on ports
of former versions ported by yerenkow.

PRs are:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231119
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231328
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232354

Version 14 does not made obsolete Version 13 and so on. For example,
version 14 is the first one java8EE certificate but there are still lots
of  people that still uses java7EE. Java8EE is retrocompatible with java7EE
but all know that bugs happen.

The last version thats current in ports , Wildfly 11, is one year old maybe
too old taking into account Wildfly versions are released quarterly.

Those are my first FreeBSD ports, so if someone can take a look and give
comments or commit them if they are OK it should be great.

They are tested and working under production in our premises.


My best regards and long live to freeBSD project!

Simeó Reig
___
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: Committer needed for new ports: archivers/urbackup-server and archivers/urbackup-client

[Kurt Jaeger]

Hi!

> > > archivers/urbackup-server: The server component from urbackup.org
> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
> > > (pending since 03/23)

Done (version 2.2.10)

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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: Committer needed for new ports: archivers/urbackup-server and archivers/urbackup-client

[Kirk Coombs]

> > archivers/urbackup-server: The server component from urbackup.org
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
> > (pending since 03/23)
>
> portlint -AC says that it needs files/urbackup_server.in --
> can you provide that startup-script ?
>

Sorry, I forgot to 'svn add' the script prior to diff'ing. Fixed.

Thanks!

Kirk

On Sun, Apr 15, 2018 at 9:59 AM, Kurt Jaeger  wrote:

> Hi!
>
> > archivers/urbackup-server: The server component from urbackup.org
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
> > (pending since 03/23)
>
> portlint -AC says that it needs files/urbackup_server.in --
> can you provide that startup-script ?
>
> > archivers/urbackup-client: The client component of the UrBackup backup
> > system
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227154
> > (pending since 04/01)
>
> testbuilds@work.
>
> --
> p...@opsec.eu+49 171 31013722 years to go !
>
___
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: Committer needed for new ports: archivers/urbackup-server and archivers/urbackup-client

[Kurt Jaeger]

Hi!

> archivers/urbackup-server: The server component from urbackup.org
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
> (pending since 03/23)

portlint -AC says that it needs files/urbackup_server.in --
can you provide that startup-script ?

> archivers/urbackup-client: The client component of the UrBackup backup
> system
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227154
> (pending since 04/01)

testbuilds@work.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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"

Committer needed for new ports: archivers/urbackup-server and archivers/urbackup-client

[Kirk Coombs]

Hello,

Can a committer please take a look at these new ports?

archivers/urbackup-server: The server component from urbackup.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
(pending since 03/23)

archivers/urbackup-client: The client component of the UrBackup backup
system
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227154
(pending since 04/01)

Thanks!

Kirk Coombs
___
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"

NEW PORTS audio/yoshimi audio/amsynth archivers/zipios

[blubee blubeeme]

Can I get someone to take a look at these ports for me

audio/yoshimi:  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223397
audio/amsynth: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223361
archivers/zipios: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223176

Thanks
___
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: committer needed for new ports: Search Guard for Kibana and Elasticsearch

[Torsten Zuehlsdorff]

Aloha,


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219739


I take this one!

Greetings,
Torsten

--
Support me at:
https://www.patreon.com/TorstenZuehlsdorff
___
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"

committer needed for new ports: Search Guard for Kibana and Elasticsearch

[Miroslav Lachman]

I submitted these two ports 2017-06-02 and there were not touched by anybody

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219738

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219739

Can somebody take a look on them?

Kind regards
Miroslav Lachman
___
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: PostgreSQL related NEW PORTS need committers

[Jov]

Hi Torsten,
  Thanks for your taking these PRs!
  miwi@ took Pgloader3 and postgresql-xl a month ago,but there was not
progress since he took it at 2017-05-13.ip4r is auto assigned to its
maintainer tobez@ but no progress since 2017-06-04.I will ping them after a
while.Thank you very much!
  For Japanese, I do not know if there is similar FTS plugin for
PostgreSQL. PG is more popular than MySQL in Japan, maybe someone in Japan
know more information.

Regard,
Jov


2017-06-30 15:38 GMT+08:00 Torsten Zuehlsdorff :

> On 30.06.2017 05:40, Jov wrote:
>
>> ​​
>> Hi hackers,
>>   I ported some PostgreSQL related tools/extensions to FreeBSD several
>> weeks
>> ago，the PR links are as follows. All of them passed portlint and tested
>> by poudriere testport. Review, comment，test or commit all are welcome，I
>> really hope some of them can be committed before Q3 quarterly branch
>> cut.Thanks very much！
>>
>> pgloader3, Replace of pgloader2 as pgloader2 is not maintained:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219165
>>
>> postgres-xl,Scalable open source PostgreSQL-based database cluster:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219164
>>
>
> There is already someone assigned to.
>
> orafce, Oracle's compatibility functions and packages for PostgreSQL:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219616
>>
>
> I'm taking it.
>
> zhparser,PostgreSQL extension for full-text search of Chinese:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219649
>>
>
> I'm taking it. (BTW: is there something similar for Japanese?)
>
> tds_fdw, PostgreSQL foreign data wrapper to connect to MS SQLserver and
>> Sybase: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219671
>>
>> pg_repack, Reorganize tables in PostgreSQL databases with minimal
>> locks.Replace of pg_reorg as it is not maintained:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219679
>>
>> plpgsql_check, PostgreSQL extension to check PL/pgSQL code:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219680
>>
>> pgformatter,PostgreSQL SQL syntax beautifier:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219681
>>
>
> I'm taking all 4. I will work through the PRs next week.
>
> ip4r（not new port，update to 2.2）:
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219766
>>
>
> This one is already assigned.
>
> Greetings,
> Torsten
> ___
> freebsd-datab...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-database
> To unsubscribe, send any mail to "freebsd-database-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: PostgreSQL related NEW PORTS need committers

[Torsten Zuehlsdorff]

On 30.06.2017 05:40, Jov wrote:

​​
Hi hackers,
  I ported some PostgreSQL related tools/extensions to FreeBSD several weeks
ago，the PR links are as follows. All of them passed portlint and tested
by poudriere testport. Review, comment，test or commit all are welcome，I
really hope some of them can be committed before Q3 quarterly branch
cut.Thanks very much！

pgloader3, Replace of pgloader2 as pgloader2 is not maintained:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219165

postgres-xl,Scalable open source PostgreSQL-based database cluster:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219164


There is already someone assigned to.


orafce, Oracle's compatibility functions and packages for PostgreSQL:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219616


I'm taking it.


zhparser,PostgreSQL extension for full-text search of Chinese:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219649


I'm taking it. (BTW: is there something similar for Japanese?)


tds_fdw, PostgreSQL foreign data wrapper to connect to MS SQLserver and
Sybase: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219671

pg_repack, Reorganize tables in PostgreSQL databases with minimal
locks.Replace of pg_reorg as it is not maintained:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219679

plpgsql_check, PostgreSQL extension to check PL/pgSQL code:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219680

pgformatter,PostgreSQL SQL syntax beautifier:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219681


I'm taking all 4. I will work through the PRs next week.


ip4r（not new port，update to 2.2）:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219766


This one is already assigned.

Greetings,
Torsten
___
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"

PostgreSQL related NEW PORTS need committers

[Jov]

​​
Hi hackers,
 I ported some PostgreSQL related tools/extensions to FreeBSD several weeks
ago，the PR links are as follows. All of them passed portlint and tested
by poudriere testport. Review, comment，test or commit all are welcome，I
really hope some of them can be committed before Q3 quarterly branch
cut.Thanks very much！

pgloader3, Replace of pgloader2 as pgloader2 is not maintained:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219165

postgres-xl,Scalable open source PostgreSQL-based database cluster:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219164

orafce, Oracle's compatibility functions and packages for PostgreSQL:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219616

zhparser,PostgreSQL extension for full-text search of Chinese:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219649

tds_fdw, PostgreSQL foreign data wrapper to connect to MS SQLserver and
Sybase: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219671

pg_repack, Reorganize tables in PostgreSQL databases with minimal
locks.Replace of pg_reorg as it is not maintained:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219679

plpgsql_check, PostgreSQL extension to check PL/pgSQL code:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219680

pgformatter,PostgreSQL SQL syntax beautifier:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219681

ip4r（not new port，update to 2.2）:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219766

Regard
Jov
___
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"

review/committer needed (new ports getting dusty)

[Dave Cottlehuber]

Hi

I added a new python port for graphite-api [0] and dependencies [1] 

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=20
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208889
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208890

www/h2o has its usual small update:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209517

thanks
Dave

[0]: http://graphite-api.readthedocs.org/ 
[1]:
https://lists.freebsd.org/pipermail/freebsd-python/2016-April/010165.html
___
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: Please commit the new ports databases/sqlite-ext-regexp and databases/sqlite-ext-spellfix - they are pending from Sep 2015

[Kurt Jaeger]

Hi!

> These are SQLite DB extensions. These are very simple ports. Somebody 
> might need them.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203217
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203218
> 
> I just updated them and made sure they build.

Done. Sorry for the delay!

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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"

Please commit the new ports databases/sqlite-ext-regexp and databases/sqlite-ext-spellfix - they are pending from Sep 2015

[Yuri]

These are SQLite DB extensions. These are very simple ports. Somebody 
might need them.


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203217
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203218

I just updated them and made sure they build.

Thanks!
Yuri

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

introducing myself + 3 new ports www/h2o net-mgmt/riemann net-p2p/swift

[Dave Cottlehuber]

Hi BSDers

By way of introduction,  I've been quietly running FreeBSD on my server
a couple of
years now, and am hoping any day for being able to run it on my laptop
too.

I'm primarily an Erlang/OTP developer, incl committer for Apache
CouchDB, mainly working
on http://www.swirl-project.org/ a not-yet-working Erlang implementation
of the PPSP protocol[6].

I've done 3 ports recently and would love some further input on what I
missed / could fix.

Riemann: Java/Clojure-based event  monitoring system
[1]: http://riemann.io/
[2]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197403

h2o: HTTP/2 server implementation in C
the project kindly made some changes to close down cleanly on FreeBSD
[3]: https://github.com/h2o/h2o
[4]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197519

swift: a LPGL C++ based implementation of the PPSP protocol
[5]: http://libswift.org/
[6]: http://tools.ietf.org/html/draft-ietf-ppsp-peer-protocol
No port submission for this as I'm waiting on upstream to commit some
build fixes and tag the repo.

All code is up at https://github.com/skunkwerks/freebsd-ports.

Thank bapt@, xmj@ who have helped me out on IRC with poudriere and
porting tips  questions.

—
  Dave Cottlehuber
  Sent from my Couch


___
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

Reference implementation of new ports

[Pavel Timofeev]

Hello!
FreeBSD's ports are going now to the new staged and optionNGed world.
Of course, freebsd porters pages have to be updated.

But, I'd like suggest something more easy, for the first glance.
Let's define a couple of ports about which we can say Yes, this port
is an example of reference implementation of our new stage+optionNG
features. This is how things must look!.
Let's support it as best practice of creating new or converting exiting ports.
I think it would really help for other maintainers as example!
These ports must contain example of that rules which was mentioned in
https://wiki.freebsd.org/ports/StageDir.
What do you think?

P.S. For some time, good place to mention about it is
https://wiki.freebsd.org/ports/StageDir. Something like For example,
look at ports path/port and path/port
___
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

why are new ports taking so long to commit

[Aryeh Friedman]

I submitted ports/185362 and ports/185361 over a week ago and I have heard
nothing but automated replies so far.
___
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: why are new ports taking so long to commit

[John Marino]

On 1/13/2014 23:05, Aryeh Friedman wrote:
 I submitted ports/185362 and ports/185361 over a week ago and I have heard
 nothing but automated replies so far.
 

There are 180 Open PRs just with the words new port in the title:
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=portsseverity=priority=class=state=sort=nonetext=new+portresponsible=multitext=originator=release=

Most of them have 2013 opening dates.  Do you still think that it's
strange that you haven't heard anything in a week?  (a week following a
major holiday btw)

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: why are new ports taking so long to commit

[Aryeh Friedman]

Only in that a earlier version I submitted last fall (which needed to be
reworked) got looked at in 2 days...


On Mon, Jan 13, 2014 at 5:18 PM, John Marino freebsd.cont...@marino.stwrote:

 On 1/13/2014 23:05, Aryeh Friedman wrote:
  I submitted ports/185362 and ports/185361 over a week ago and I have
 heard
  nothing but automated replies so far.
 

 There are 180 Open PRs just with the words new port in the title:

 http://www.freebsd.org/cgi/query-pr-summary.cgi?category=portsseverity=priority=class=state=sort=nonetext=new+portresponsible=multitext=originator=release=

 Most of them have 2013 opening dates.  Do you still think that it's
 strange that you haven't heard anything in a week?  (a week following a
 major holiday btw)

 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

___
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: why are new ports taking so long to commit

[Pascal Schmid]

On 01/13/2014 11:05 PM, Aryeh Friedman wrote:
 I submitted ports/185362 and ports/185361 over a week ago and I have heard
 nothing but automated replies so far.
 ___
 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
 

Please be patient. There are many opened port commits, but not enough
volunteers for handling all of them fast.
My port was submitted in September and I still have no response... ;)
___
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: why are new ports taking so long to commit

[Fernando Apesteguía]

El 13/01/2014 23:27, Pascal Schmid pas...@lechindianer.de escribió:

 On 01/13/2014 11:05 PM, Aryeh Friedman wrote:
  I submitted ports/185362 and ports/185361 over a week ago and I have
heard
  nothing but automated replies so far.
  ___
  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
 

 Please be patient. There are many opened port commits, but not enough
 volunteers for handling all of them fast.
 My port was submitted in September and I still have no response... ;)

I sent mine in November, then I was asked to update it since there was a
new version upstream. I did it but it's not in the ports tree yet.

So... In perspective, you're lucky :)

 ___
 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: portmaster -w -r icu wants to install new ports

[Chess Griffin]

On Thu, Dec 27, 2012, at 09:32 PM, Kevin Oberman wrote:
 As I often do, I recommend using pkg_libchk -o | grep libicu | cut -f1
 -d: | sort | uniq' to provide a list of the ports that actually link
 to the shareable libraries in icu. Those are the only ports you really
 need to re-install. Walking up the dependency tree will catch many
 ports that depend on comething that links to a shareable, but don't
 link to it, itself.
 

Thanks, this did seem to help.  After doing this and rerunning
portmaster I think I got the list down to the installed ports.  In any
event, all is updated and working well.  Cheers!

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

portmaster -w -r icu wants to install new ports

[Chess Griffin]

Hi - I just updated my ports tree with portsnap and, per UPDATING, ran
portmaster -w -r icu to rebuild ports that depend on icu.  However,
portmaster also listed a long list of new ports it was going to build
and install -- things like shells/bash and a lot from x11/.  Is this
intended behavior?  I thought portmaster -w -r icu would only build and
reinstall all installed ports that depend on icu.  Can't say I've come
across portmaster doing this before but maybe I'm just forgetful in my
old age.  :-) 

Thanks.

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

Re: portmaster -w -r icu wants to install new ports

[Kevin Oberman]

On Thu, Dec 27, 2012 at 6:08 PM, Chess Griffin ch...@chessgriffin.com wrote:
 Hi - I just updated my ports tree with portsnap and, per UPDATING, ran
 portmaster -w -r icu to rebuild ports that depend on icu.  However,
 portmaster also listed a long list of new ports it was going to build
 and install -- things like shells/bash and a lot from x11/.  Is this
 intended behavior?  I thought portmaster -w -r icu would only build and
 reinstall all installed ports that depend on icu.  Can't say I've come
 across portmaster doing this before but maybe I'm just forgetful in my
 old age.  :-)

This is probably what it is supposed to do. It will upgrade icu anjd
re-install every port that has icu as a dependency. It will also
install any dependency of any port that it re-installs that is either
out of date or missing.
Often these are really not required for a given system.

As I often do, I recommend using pkg_libchk -o | grep libicu | cut -f1
-d: | sort | uniq' to provide a list of the ports that actually link
to the shareable libraries in icu. Those are the only ports you really
need to re-install. Walking up the dependency tree will catch many
ports that depend on comething that links to a shareable, but don't
link to it, itself.

pkg_libchk is a part of sysutils/bsdadminscripts and I highly
recommend it for dealing with shareable library version bumps. It will
save you a LOT of time. If you just run hte script, it will catch any
other dependency problems that might be hanging around on a system,
but it WILL produce false positives for a few ports which don't rely
on the standard system tool (rtld) for loading sharables. openjdk is a
common isue and openoffice used to do this. Don't know if it still
does since I use libreoffice.
-- 
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

New ports - Bullet Cache

[Ivan Voras]

Hello,

I've submitted a couple of new ports, and I'd like to ask someone to
take a look at them and commit them:

http://www.freebsd.org/cgi/query-pr.cgi?pr=164872

I'm not sure how to handle the shared library installation issue (lines
36,37 in mdcached/Makefile).



signature.asc
Description: OpenPGP digital signature

portmaster: Installing new ports without upgrading already installed ones ?

[Marco Steinbach]

Hi there,

is there a way for telling portmaster to not upgrade already installed 
dependencies, besides explicitly excluding these with '-x' or using 
'+IGNOREME' ?


In other words:  Is there a flag, or a combination thereof, to have 
portmaster conveniently just install missing and not upgrade allready 
installed dependencies -- like a 'make install' in a ports' directory 
would do ?


I'm using portmaster 3.11.

MfG CoCo

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

Re: portmaster: Installing new ports without upgrading already installed ones ?

[geoffroy desvernay]

On 15.02.2012 15:04, Marco Steinbach wrote:
 Hi there,
 
 is there a way for telling portmaster to not upgrade already installed
 dependencies, besides explicitly excluding these with '-x' or using
 '+IGNOREME' ?
 
 In other words:  Is there a flag, or a combination thereof, to have
 portmaster conveniently just install missing and not upgrade allready
 installed dependencies -- like a 'make install' in a ports' directory
 would do ?
 
 I'm using portmaster 3.11.
 
 MfG CoCo
 

portmaster -i may let you decide what to update...

HTH
-- 
*geoffroy desvernay*
C.R.I - Administration systèmes et réseaux
Ecole Centrale de Marseille



signature.asc
Description: OpenPGP digital signature

Re: portmaster: Installing new ports without upgrading already installed ones ?

[Marco Steinbach]

geoffroy desvernay wrote on 15.02.2012 18:24:

On 15.02.2012 15:04, Marco Steinbach wrote:

Hi there,

is there a way for telling portmaster to not upgrade already installed
dependencies, besides explicitly excluding these with '-x' or using
'+IGNOREME' ?

In other words:  Is there a flag, or a combination thereof, to have
portmaster conveniently just install missing and not upgrade allready
installed dependencies -- like a 'make install' in a ports' directory
would do ?

I'm using portmaster 3.11.

MfG CoCo



portmaster -i may let you decide what to update...



Thanks for the hint -- Alas, going interactive kind of ends me up doing 
what I described in the first paragraph, just by other means.


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

Re: portmaster: Installing new ports without upgrading already installed ones ?

[Doug Barton]

On 02/15/2012 06:04, Marco Steinbach wrote:
 Hi there,
 
 is there a way for telling portmaster to not upgrade already installed
 dependencies, besides explicitly excluding these with '-x' or using
 '+IGNOREME' ?

Someone already mentioned -i.

 In other words:  Is there a flag, or a combination thereof, to have
 portmaster conveniently just install missing and not upgrade allready
 installed dependencies -- like a 'make install' in a ports' directory
 would do ?

To answer your question, no. The tool is not designed to be used that
way. (And no, I won't add that as an option.)


hth,

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: portmaster: Installing new ports without upgrading already installed ones ?

[Marco Steinbach]

On Wed, 15 Feb 2012, Doug Barton wrote:


On 02/15/2012 06:04, Marco Steinbach wrote:

Hi there,

is there a way for telling portmaster to not upgrade already installed
dependencies, besides explicitly excluding these with '-x' or using
'+IGNOREME' ?


Someone already mentioned -i.


In other words:  Is there a flag, or a combination thereof, to have
portmaster conveniently just install missing and not upgrade allready
installed dependencies -- like a 'make install' in a ports' directory
would do ?


To answer your question, no. The tool is not designed to be used that
way. (And no, I won't add that as an option.)


Fair enough -- thanks for the clarification.  And for maintaining portmaster
in the first place, of course.

MfG CoCo

___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Lev Serebryakov]

Hello, Perryh.
You wrote 11 сентября 2011 г., 10:05:59:

 I can't address the non-specific etc, but I would claim that each
 of those 3 specific examples is a VCS bug.  Creating a tarball of a
 particular content set _should_ be a deterministic process:
 Once again: gzip, for example, has timestamp field in header. Try
 this locally, without any [D]VCS:

% mkdir test  echo one  test/one.txt  echo two  test/two.txt
% tar czf test1.tar.gz test  sleep 5  tar czf test2.tar.gz test
% md5 test1.tar.gz test2.tar.gz
MD5 (test1.tar.gz) = 7b7c763a9d1d4edca7b5b415ab297fec
MD5 (test2.tar.gz) = 703ac5387b2bd1146434516f1d761ed9
% gzip -d test1.tar.gz test2.tar.gz
% md5 test1.tar test2.tar
MD5 (test1.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85
MD5 (test2.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85
%



-- 
// Black Lion AKA Lev Serebryakov l...@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: [RFC] New ports idea: github / gitorious / bitbucket

[C-S]

Sure it worth. From my POV, maintainer should be avoided the pleasure to 
 mess with selfhosted and selfpackaged tarballs as much as possible. 
 Besides of inconvenience it also less reliable (both in availability and 
 security aspects).
 
  I'm perfectly happy to mirror anything if needed, by the way.
 
  Chris
 

Selfhosting can be very helpful. I once had many downloads of hiawatha
from my server in my logs. So, I checked the hashes and discovered that
the distfile from the original homepage was not the same anymore. The
author of hiawatha had changed the file without any announcements...

Carlo

___
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: [RFC] New ports idea: github / gitorious / bitbucket

[Ruslan Mahmatkhanov]

C-S wrote on 11.09.2011 17:23:

Sure it worth. From my POV, maintainer should be avoided the pleasure to
mess with selfhosted and selfpackaged tarballs as much as possible.
Besides of inconvenience it also less reliable (both in availability and
security aspects).


I'm perfectly happy to mirror anything if needed, by the way.

Chris




Selfhosting can be very helpful. I once had many downloads of hiawatha
from my server in my logs. So, I checked the hashes and discovered that
the distfile from the original homepage was not the same anymore. The
author of hiawatha had changed the file without any announcements...

Carlo


We will see that anyway - when user will try to extract changed 
distfile, he will get warning about incorrect checksum, so this is not 
the case, i believe.


--
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: [RFC] New ports idea: github / gitorious / bitbucket

[Ruslan Mahmatkhanov]

Ruslan Mahmatkhanov wrote on 11.09.2011 23:50:


We will see that anyway - when user will try to extract changed
distfile, he will get warning about incorrect checksum, so this is not
the case, i believe.


s/warning/error/g

this error will stops the build.

--
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: [RFC] New ports idea: github / gitorious / bitbucket

[C-S]

On Sun, 2011-09-11 at 23:52 +0400, Ruslan Mahmatkhanov wrote:
 Ruslan Mahmatkhanov wrote on 11.09.2011 23:50:
 
  We will see that anyway - when user will try to extract changed
  distfile, he will get warning about incorrect checksum, so this is not
  the case, i believe.
 
 s/warning/error/g
 
 this error will stops the build.
 

Of course. I am not worried about the user, but from a maintainer's
point of view it is helpful to get informed about that. Unless you check
all your port's distfile hashes all the time it takes some time to
discover if you have a bad mirror (and all other mirrors being fine).

___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Peter Pentchev]

On Sun, Sep 11, 2011 at 01:01:31PM +0400, Lev Serebryakov wrote:
 Hello, Perryh.
 You wrote 11 сентября 2011 г., 10:05:59:
 
  I can't address the non-specific etc, but I would claim that each
  of those 3 specific examples is a VCS bug.  Creating a tarball of a
  particular content set _should_ be a deterministic process:
  Once again: gzip, for example, has timestamp field in header. Try
  this locally, without any [D]VCS:
 
 % mkdir test  echo one  test/one.txt  echo two  test/two.txt
 % tar czf test1.tar.gz test  sleep 5  tar czf test2.tar.gz test
 % md5 test1.tar.gz test2.tar.gz
 MD5 (test1.tar.gz) = 7b7c763a9d1d4edca7b5b415ab297fec
 MD5 (test2.tar.gz) = 703ac5387b2bd1146434516f1d761ed9
 % gzip -d test1.tar.gz test2.tar.gz
 % md5 test1.tar test2.tar
 MD5 (test1.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85
 MD5 (test2.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85
 %

Now try the same with the -n option :)

(and yes, I realize that you are probably aware of this, but so should
 any author of a system that automatically creates compressed tarballs
 out of not-ridigly-structured data)

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@freebsd.org pe...@packetscale.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
No language can express every thought unambiguously, least of all this one.


signature.asc
Description: Digital signature

Re: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[perryh]

Lev Serebryakov l...@freebsd.org wrote:

  ... gzip, for example, has timestamp field in header.
  Try this locally, without any [D]VCS:

 % mkdir test  echo one  test/one.txt  echo two  test/two.txt
 % tar czf test1.tar.gz test  sleep 5  tar czf test2.tar.gz test
 % md5 test1.tar.gz test2.tar.gz
 MD5 (test1.tar.gz) = 7b7c763a9d1d4edca7b5b415ab297fec
 MD5 (test2.tar.gz) = 703ac5387b2bd1146434516f1d761ed9
 % gzip -d test1.tar.gz test2.tar.gz
 % md5 test1.tar test2.tar
 MD5 (test1.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85
 MD5 (test2.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85

That is arguably a bug in tar czf :)  but it is easy enough to
work around; we just need a checksum method -- e.g. SHA256_UNGZ --
that pipes the distfile through gunzip when computing its checksum.
___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[b. f.]

   ... gzip, for example, has timestamp field in header.
   Try this locally, without any [D]VCS:
 
  % mkdir test  echo one  test/one.txt  echo two  test/two.txt
  % tar czf test1.tar.gz test  sleep 5  tar czf test2.tar.gz test
  % md5 test1.tar.gz test2.tar.gz
  MD5 (test1.tar.gz) = 7b7c763a9d1d4edca7b5b415ab297fec
  MD5 (test2.tar.gz) = 703ac5387b2bd1146434516f1d761ed9
  % gzip -d test1.tar.gz test2.tar.gz
  % md5 test1.tar test2.tar
  MD5 (test1.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85
  MD5 (test2.tar) = 0ba33aa8ff6bffeeeb2d96efc38eec85

 That is arguably a bug in tar czf :)  but it is easy enough to
 work around; we just need a checksum method -- e.g. SHA256_UNGZ --
 that pipes the distfile through gunzip when computing its checksum.


The problem goes beyond that: different standard tar formats can
include mutable data like major and minor device numbers, and the
atimes, uids, and gids of files.  See, for example, tar(5). We would
have to continually monitor whether each site generates tarballs with
invariant checksums from the same files, or check the integrity of
archive members after extraction.

b.
___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[perryh]

Baptiste Daroussin b...@freebsd.org wrote:

 The main problem with that is: we have no way to keep a valid sum
 of the distfiles if it is autogenerated (in particular with github)
 and this sum is really important.

No question about the importance of the checksum, to prevent trojans
and other problems if the distfile were to change silently.

If I am understanding correctly, you seem to be saying that two
distfiles autogenerated from the _same_ tag etc. in the _same_
repository, and actually containing exactly the same code, can
nevertheless generate different checksums!?  Wouldn't that be a
bug in the DVCS?
___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Lev Serebryakov]

Hello, Perryh.
You wrote 10 сентября 2011 г., 18:03:41:

 If I am understanding correctly, you seem to be saying that two
 distfiles autogenerated from the _same_ tag etc. in the _same_
 repository, and actually containing exactly the same code, can
 nevertheless generate different checksums!?  Wouldn't that be a
 bug in the DVCS?
 If archive contains timestamp of its creation in header, checksums of
ARCHIVE will be different for sure.

-- 
// Black Lion AKA Lev Serebryakov l...@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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Shaun Amott]

On Fri, Sep 09, 2011 at 04:39:14PM +0100, Klaus T. Aehlig wrote:
 
  Until recently, github required two requests to get a tarball: one to
  initiate the tarball creation, the other to download it.
 
 Yes, that's what I remember. The URL you got after the first redirect
 was then good for a couple of days -- till eventually it wasn't used
 for long enough time and the initial request was necessary again to
 initiate tarball creation once again.
 
 When did they change that? That's definitely good news.

The change occurred sometime in the last few months. This might be
related:

https://github.com/blog/900-nodeload2-downloads-reloaded

-- 
Shaun Amott // PGP: 0x6B387A9A
A foolish consistency is the hobgoblin
of little minds. - Ralph Waldo Emerson


pgpt31kI015Db.pgp
Description: PGP signature

Re: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Chris Rees]

On 9 September 2011 15:28, Baptiste Daroussin b...@freebsd.org wrote:
 On Fri, Sep 09, 2011 at 02:24:37PM +0100, Klaus T. Aehlig wrote:
  The main problem with that is: we have no way to keep a valid sum of the
  distfiles if it is autogenerated (in particular with github) and this sum 
  is
  really important.
 With github this fortunately is a non-issue. Even though they autogenerate 
 their
 tar balls, they keep enough information to make them reproduciable. Just try:

 /tmpfetch https://github.com/Dieterbe/uzbl/tarball/2011.07.25
 2011.07.25                                    100% of  143 kB  177 kBps
 /tmpsha256 2011.07.25
 SHA256 (2011.07.25) = 
 2e61fa6c62e48d3f13e95a4ea7e7aead65345f6c88a688844ef921685dffe565
 /tmpcat /usr/ports/www/uzbl/distinfo
 SHA256 (uzbl-0.0.0.2011.07.25.tar.gz) = 
 2e61fa6c62e48d3f13e95a4ea7e7aead65345f6c88a688844ef921685dffe565
 SIZE (uzbl-0.0.0.2011.07.25.tar.gz) = 146851
 /tmp

 There still remain some minor issuses, like

 * due to autogeneration, you're quite likely to get a http-redirect,
 * filenames like 2011.07.25 are not too suitable for a distfile.

 But they certainly can be fixed by an appropriate framework. The nice thing 
 is,
 github does the autogeneration right.

 Best,
 Klaus


 This is new because I already poke them about this in the past (more than a 
 year
 ago and they clearly stated that they can't change that and that github people
 shouldn't use this for realease but should use the real download space of
 github)

 The issue opened about this seems to have disapear from github, maybe they
 change their mind


I agree 100% with Bapt here-- I had the same problem with
security/gorilla (I think it was gorilla...) -- the tarball wasn't
stable over time and I had many problems with distinfo.

I solved the problem, as Bapt suggested by approaching the author and
politely asking if he would host the tarball on github. He agreed to
do this.

Most of the time developers using github simply overlook the problems
of autogenerated tarballs, and just don't think to host dedicated ones
-- I've never had a negative response from upstream about providing a
proper stable tarball.

Counterexamples welcome!

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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Ruslan Mahmatkhanov]

Chris Rees wrote on 10.09.2011 21:33:


Counterexamples welcome!

Chris


When i worked on net/erlyvideo port there on github were tarballs for 
some old versions of it. When i asked author to create tarballs for new 
versions too, he just delete all the tarballs :)

So i just create and host them by myself.

--
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Chris Rees]

On 10 September 2011 18:47, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
 Chris Rees wrote on 10.09.2011 21:33:


 Counterexamples welcome!

 Chris

 When i worked on net/erlyvideo port there on github were tarballs for some
 old versions of it. When i asked author to create tarballs for new versions
 too, he just delete all the tarballs :)
 So i just create and host them by myself.


Hm, plain spiteful.  I like to think (or hope) that's not
representative of most of our upstream friends ;)

The main question is, is it worth us writing code to handle a small
minority of projects that refuse, or is it just easier to host this
same minority ourselves?

I'm perfectly happy to mirror anything if needed, by the way.

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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Ruslan Mahmatkhanov]

Chris Rees wrote on 10.09.2011 21:58:

On 10 September 2011 18:47, Ruslan Mahmatkhanovcvs-...@yandex.ru  wrote:

Chris Rees wrote on 10.09.2011 21:33:



Counterexamples welcome!

Chris


When i worked on net/erlyvideo port there on github were tarballs for some
old versions of it. When i asked author to create tarballs for new versions
too, he just delete all the tarballs :)
So i just create and host them by myself.



Hm, plain spiteful.  I like to think (or hope) that's not
representative of most of our upstream friends ;)


Yep, for the second (and last) example - mediacore guys also ignored my 
request. But they use tags on github and has tarballs on main website.




The main question is, is it worth us writing code to handle a small
minority of projects that refuse, or is it just easier to host this
same minority ourselves?


Sure it worth. From my POV, maintainer should be avoided the pleasure to 
mess with selfhosted and selfpackaged tarballs as much as possible. 
Besides of inconvenience it also less reliable (both in availability and 
security aspects).



I'm perfectly happy to mirror anything if needed, by the way.

Chris



--
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Klaus T. Aehlig]

 The change occurred sometime in the last few months. This might be
 related:
 
 https://github.com/blog/900-nodeload2-downloads-reloaded

Ah, I see. Thanks for the link.

Klaus
___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[perryh]

Matthew D. Fuller fulle...@over-yonder.net wrote:
 On Sat, Sep 10, 2011 at 07:03:41AM -0700 I heard the voice of
 per...@pluto.rain.com, and lo! it spake thus:
  
  If I am understanding correctly, you seem to be saying that two
  distfiles autogenerated from the _same_ tag etc. in the _same_
  repository, and actually containing exactly the same code, can
  nevertheless generate different checksums!?  Wouldn't that be a
  bug in the DVCS?

 There're all sorts of ways the same content could wind up with
 different checksums.  The compression may happen slightly differently,
 higher, or lower.  The files could wind up in the tarball in a
 different order.  Timestamps could differ.  etc.

I can't address the non-specific etc, but I would claim that each
of those 3 specific examples is a VCS bug.  Creating a tarball of a
particular content set _should_ be a deterministic process:

* The compression method, and the ordering of the files, should be
  consistent.

* Each file's timestamp in the tarball should be the selected
  version's timestamp as recorded in the repository, typically the
  time when the selected version of that file was committed to the
  VCS.  Ditto for directories, provided the VCS maintains directory
  history.

* If the VCS does _not_ maintain directory history (which is a
  deficiency, but not really a bug), each directory's timestamp
  in the tarball should match the most-recent file or subdirectory
  in that directory.
___
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

[RFC] New ports idea: github / gitorious / bitbucket direct support.

[Lev Serebryakov]

Hello, Freebsd-ports.

  I notice, that many software projects are hosted on social DVCS
hostings nowadays.

  Other common feature among them is absence of official tarballs
for versions. I don't say, that ALL projects whith primary hosting on
these DVCS sites don't publish official tarballs. But many of them
don't.

  On other hand, all these DVCS sites provide way to download auto-generated 
tarballs
for any tag or branch or revision.

  Maybe, we need support for this model to ports system directly? Like
we support SourceForge and other code hosting sites.

-- 
// Black Lion AKA Lev Serebryakov l...@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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Baptiste Daroussin]

On Fri, Sep 09, 2011 at 02:30:52PM +0400, Lev Serebryakov wrote:
 Hello, Freebsd-ports.
 
   I notice, that many software projects are hosted on social DVCS
 hostings nowadays.
 
   Other common feature among them is absence of official tarballs
 for versions. I don't say, that ALL projects whith primary hosting on
 these DVCS sites don't publish official tarballs. But many of them
 don't.
 
   On other hand, all these DVCS sites provide way to download auto-generated 
 tarballs
 for any tag or branch or revision.
 
   Maybe, we need support for this model to ports system directly? Like
 we support SourceForge and other code hosting sites.
 

The main problem with that is: we have no way to keep a valid sum of the
distfiles if it is autogenerated (in particular with github) and this sum is
really important.

regards,
Bapt


pgpmHhPdusTdh.pgp
Description: PGP signature

Re: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Klaus T. Aehlig]

 The main problem with that is: we have no way to keep a valid sum of the
 distfiles if it is autogenerated (in particular with github) and this sum is
 really important.


With github this fortunately is a non-issue. Even though they autogenerate their
tar balls, they keep enough information to make them reproduciable. Just try:

/tmpfetch https://github.com/Dieterbe/uzbl/tarball/2011.07.25
2011.07.25100% of  143 kB  177 kBps
/tmpsha256 2011.07.25 
SHA256 (2011.07.25) = 
2e61fa6c62e48d3f13e95a4ea7e7aead65345f6c88a688844ef921685dffe565
/tmpcat /usr/ports/www/uzbl/distinfo 
SHA256 (uzbl-0.0.0.2011.07.25.tar.gz) = 
2e61fa6c62e48d3f13e95a4ea7e7aead65345f6c88a688844ef921685dffe565
SIZE (uzbl-0.0.0.2011.07.25.tar.gz) = 146851
/tmp

There still remain some minor issuses, like

* due to autogeneration, you're quite likely to get a http-redirect,
* filenames like 2011.07.25 are not too suitable for a distfile.

But they certainly can be fixed by an appropriate framework. The nice thing is,
github does the autogeneration right.

Best,
Klaus

___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Lev Serebryakov]

Hello, Baptiste.
You wrote 9 сентября 2011 г., 17:04:58:

 The main problem with that is: we have no way to keep a valid sum of the
 distfiles if it is autogenerated (in particular with github) and this sum is
 really important.
 I've thought about checksums, but my simple experiment shows, that
tag-related (not tip-related, of course) archives give same chsum
after re-downloading in short time. But I don't check it for long-term
stability.

 Ok, other idea: check-out sources (require hg/git as BUILD
dependency, but anyway user will need them to build software by hands)
and check strong checksum of checked out revision (as both DVCS uses
strong checksums as IDs internally).

 It is more complex feature, than adding additional MASTER_SITES, for
sure.

-- 
// Black Lion AKA Lev Serebryakov l...@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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Klaus T. Aehlig]

  I've thought about checksums, but my simple experiment shows, that
 tag-related (not tip-related, of course) archives give same chsum
 after re-downloading in short time. But I don't check it for long-term
 stability.

Well, let's do at least one check with a one and a half year old tar ball.

[root@kta1c10 /tmp]# fetch https://github.com/Dieterbe/uzbl/tarball/2010.01.05
2010.01.05100% of  130 kB  320 kBps
[root@kta1c10 /tmp]# sha256 2010.01.05 
SHA256 (2010.01.05) = 
0aae5c9994d968b4f4ec7f8f2ce935c25e25d19cabbce27e3ded0672756132c8
[root@kta1c10 /tmp]# cd /usr/ports/www/uzbl/
[root@kta1c10 /usr/ports/www/uzbl]# cvs diff -r1.1 distinfo 
Index: distinfo
===
RCS file: /usr/ctm/cvs-cur/ports/www/uzbl/distinfo,v
retrieving revision 1.1
retrieving revision 1.11
diff -r1.1 -r1.11
1,3c1,2
 MD5 (uzbl-0.0.0.2010.01.05.tar.gz) = 2574fc68a7a7693297d371ca58a4edb4
 SHA256 (uzbl-0.0.0.2010.01.05.tar.gz) = 
0aae5c9994d968b4f4ec7f8f2ce935c25e25d19cabbce27e3ded0672756132c8
 SIZE (uzbl-0.0.0.2010.01.05.tar.gz) = 133875
---
 SHA256 (uzbl-0.0.0.2011.07.25.tar.gz) = 
 2e61fa6c62e48d3f13e95a4ea7e7aead65345f6c88a688844ef921685dffe565
 SIZE (uzbl-0.0.0.2011.07.25.tar.gz) = 146851
[root@kta1c10 /usr/ports/www/uzbl]# 

There it works as well...

Best,
Klaus

___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Lev Serebryakov]

Hello, Klaus.
You wrote 9 сентября 2011 г., 17:24:37:


 * due to autogeneration, you're quite likely to get a http-redirect,
 Does fetch support redirects?

 * filenames like 2011.07.25 are not too suitable for a distfile.
 DIST_SUBIDR=${PORTNAME} is solution for this.

-- 
// Black Lion AKA Lev Serebryakov l...@serebryakov.spb.ru

___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Klaus T. Aehlig]

  * due to autogeneration, you're quite likely to get a http-redirect,
  Does fetch support redirects?

Yes. But for good reasons, Mk/bsd.ports.mk contains the line

FETCH_ARGS?=-AFpr

Note the -A. Of course, it's no problem to make an exception for github, but
at least, one should be aware of this.

  * filenames like 2011.07.25 are not too suitable for a distfile.
  DIST_SUBIDR=${PORTNAME} is solution for this.

yes. And a github framework probably should set this by default...

Best,
Klaus

___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Baptiste Daroussin]

On Fri, Sep 09, 2011 at 02:24:37PM +0100, Klaus T. Aehlig wrote:
 
 
  The main problem with that is: we have no way to keep a valid sum of the
  distfiles if it is autogenerated (in particular with github) and this sum is
  really important.
 
 
 With github this fortunately is a non-issue. Even though they autogenerate 
 their
 tar balls, they keep enough information to make them reproduciable. Just try:
 
 /tmpfetch https://github.com/Dieterbe/uzbl/tarball/2011.07.25
 2011.07.25100% of  143 kB  177 kBps
 /tmpsha256 2011.07.25 
 SHA256 (2011.07.25) = 
 2e61fa6c62e48d3f13e95a4ea7e7aead65345f6c88a688844ef921685dffe565
 /tmpcat /usr/ports/www/uzbl/distinfo 
 SHA256 (uzbl-0.0.0.2011.07.25.tar.gz) = 
 2e61fa6c62e48d3f13e95a4ea7e7aead65345f6c88a688844ef921685dffe565
 SIZE (uzbl-0.0.0.2011.07.25.tar.gz) = 146851
 /tmp
 
 There still remain some minor issuses, like
 
 * due to autogeneration, you're quite likely to get a http-redirect,
 * filenames like 2011.07.25 are not too suitable for a distfile.
 
 But they certainly can be fixed by an appropriate framework. The nice thing 
 is,
 github does the autogeneration right.
 
 Best,
 Klaus
 

This is new because I already poke them about this in the past (more than a year
ago and they clearly stated that they can't change that and that github people
shouldn't use this for realease but should use the real download space of
github)

The issue opened about this seems to have disapear from github, maybe they
change their mind

regards,
Bapt


pgpzmDDTJ4Neb.pgp
Description: PGP signature

Re: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Klaus T. Aehlig]

 Until recently, github required two requests to get a tarball: one to
 initiate the tarball creation, the other to download it.

Yes, that's what I remember. The URL you got after the first redirect
was then good for a couple of days -- till eventually it wasn't used
for long enough time and the initial request was necessary again to
initiate tarball creation once again.

When did they change that? That's definitely good news.

Klaus
___
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: [RFC] New ports idea: github / gitorious / bitbucket direct support.

[Shaun Amott]

On Fri, Sep 09, 2011 at 03:05:42PM +0100, Klaus T. Aehlig wrote:
   * due to autogeneration, you're quite likely to get a http-redirect,
   Does fetch support redirects?
 
 Yes. But for good reasons, Mk/bsd.ports.mk contains the line
 
 FETCH_ARGS?=-AFpr
 
 Note the -A. Of course, it's no problem to make an exception for github, but
 at least, one should be aware of this.

The redirect is often avoidable if you can determine the final URL of
the distfile. Github only uses a single hostname for tarball downloads,
so there is no issue with maintaining a list of mirrors.

Until recently, github required two requests to get a tarball: one to
initiate the tarball creation, the other to download it. I was able to
work around this in one of my ports, but the hack is no longer needed.

-- 
Shaun Amott // PGP: 0x6B387A9A
A foolish consistency is the hobgoblin
of little minds. - Ralph Waldo Emerson


pgpRTUDcBWUnD.pgp
Description: PGP signature

updates to pending new ports

[Klaus T. Aehlig]

Hi,

Recently, I submitted PR ports/141674 suggesting a port for the uzbl
web browser. Given the current holiday season, I'm not surprised that
it is still unassigned. On the other hand, upstream has developped
further, and I wonder if I'm right in submitting updated versions of
this port as followups to the PR. (My thoughts went along the lines 
If it's still unassigned, then probably no committer has spent any 
time on it; so when it gets assigned to a commiter, (s)he might as well
look at a port for the latest version.) Or should I consider the
fact that the PR is unassigned as a sign that this port is
probably not interesting for FreeBSD?

[Since I'm using that browser on my private machine, I'm updating
the port anyway, so it's no extra work for me to submit follow
ups. I'm just wondering whether this is what I'm supposed to do,
or just considered annoying.]

Best regards and happy new year!

Klaus

___
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: updates to pending new ports

[Matthew Seaman]

Klaus T. Aehlig wrote:

Hi,

Recently, I submitted PR ports/141674 suggesting a port for the uzbl
web browser. Given the current holiday season, I'm not surprised that
it is still unassigned. On the other hand, upstream has developped
further, and I wonder if I'm right in submitting updated versions of
this port as followups to the PR. (My thoughts went along the lines 
If it's still unassigned, then probably no committer has spent any 
time on it; so when it gets assigned to a commiter, (s)he might as well

look at a port for the latest version.) Or should I consider the
fact that the PR is unassigned as a sign that this port is
probably not interesting for FreeBSD?

[Since I'm using that browser on my private machine, I'm updating
the port anyway, so it's no extra work for me to submit follow
ups. I'm just wondering whether this is what I'm supposed to do,
or just considered annoying.]


It's certainly better to submit updates by following up on an already open
ticket, rather than creating a whole raft of new tickets.

Updating your port before it is committed does indicate a certain degree of 
commitment to keeping the port up to date, which is a good thing.


You can't really assume anything about the status of your submission if it
is still unassigned.  All that really means is that no one has yet taken
responsibility for checking and committing it.  If there were any questions
as to whether the port should be added to the tree at all, then they would be
coming to you from the committer that had assigned the PR to themselves.  If
your new port has been languishing unassigned for a long time (I'd say a few
weeks at least), it's legitimate to ask about its status on this list -- as
you say, submitting the port during the holiday season may well have slipped
it under the radar of anyone that might work on it.

Cheers,

Matthew

--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

New Ports: OWAMP

[Guilherme Eliseu Rhoden]

Hi all,

I've ported owamp (OneWay PING - OneWay active measurement protocol) to 
FreeBSD ports.


I can upload the code to ports CVS. How can I create an CSV accounting 
to do this?

I can't find this steps on the ports documentation.

Thanks,
Guilherme
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: New Ports: OWAMP

[Pietro Cerutti]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Guilherme Eliseu Rhoden wrote:
| Hi all,
|
| I've ported owamp (OneWay PING - OneWay active measurement protocol) to
| FreeBSD ports.
|
| I can upload the code to ports CVS. How can I create an CSV accounting
| to do this?

You can't. CVS isn't open for commits.
You better fill-in a PR [1] with your port attached and let someone with
CVS write access commit it.

[1] http://www.freebsd.org/support/bugreports.html

| Thanks,

Thanks,

| Guilherme


- --
Pietro Cerutti
[EMAIL PROTECTED]

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEAREKAAYFAkhWvX4ACgkQwMJqmJVx945TugCeMlwKN84OvGr2FKG4mlx0FyRv
lDAAoLq6T/6GJHBBeBQxhLFoTkFxId84
=9Vgk
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Commiting new ports

[Rodrigo OSORIO (ros)]

Hello,

I take advantage of this discussion to refer to my own port submission 
(ports/123614)
open from 12 may, a short delay of course, but I will be very happy to see it 
aproved ;)


Thanks
Rodrigo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Commiting new ports

[Nikolaj Thygesen]

Sahil Tandon wrote:

Wesley Shields [EMAIL PROTECTED] wrote:

  

On Fri, Jun 06, 2008 at 12:56:48AM +0200, Nikolaj Thygesen wrote:


Hi,

I hope this is the right list to ask this question. I recently 
commited a new port, and received two messages from ports. The first 
one noted that a person had assigned the port to himself, and the second 
mail simply stated that the PR went from open to closed due to 
feedback timeout. I reckon this means the port was rejected, but have 
no clue for what reason. Was I supposed to supply any kind of feedback 
somewhere??
  

I would suggest following up with the person who closed the PR (which I
assume was the same person it was assigned to).  There is a good chance
the feedback request was not seen by you for any number of reasons.
Lastly, the feedback being requested should also be in the audit-trail
of the PR if possible, so you may be able to look there if you have not
already.

Without more information I'm afraid we can't help you further.  We would
need, at a minimum, the PR number to follow up.



http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/123239

Perhaps Martin sought feedback from Nikolaj via email and did not receive a 
reply.
   
  
As previously reported the port was closed due to a mail bounce, and it 
has been reopened, so all is well!


Thanks - Nikolaj

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

Commiting new ports

[Nikolaj Thygesen]

Hi,

   I hope this is the right list to ask this question. I recently 
commited a new port, and received two messages from ports. The first 
one noted that a person had assigned the port to himself, and the second 
mail simply stated that the PR went from open to closed due to 
feedback timeout. I reckon this means the port was rejected, but have 
no clue for what reason. Was I supposed to supply any kind of feedback 
somewhere??



   br - Nikolaj

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

Re: Commiting new ports

[Wesley Shields]

On Fri, Jun 06, 2008 at 12:56:48AM +0200, Nikolaj Thygesen wrote:
 Hi,
 
 I hope this is the right list to ask this question. I recently 
 commited a new port, and received two messages from ports. The first 
 one noted that a person had assigned the port to himself, and the second 
 mail simply stated that the PR went from open to closed due to 
 feedback timeout. I reckon this means the port was rejected, but have 
 no clue for what reason. Was I supposed to supply any kind of feedback 
 somewhere??

I would suggest following up with the person who closed the PR (which I
assume was the same person it was assigned to).  There is a good chance
the feedback request was not seen by you for any number of reasons.
Lastly, the feedback being requested should also be in the audit-trail
of the PR if possible, so you may be able to look there if you have not
already.

Without more information I'm afraid we can't help you further.  We would
need, at a minimum, the PR number to follow up.

-- WXS
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Commiting new ports

[Matthew Donovan]

On Fri, Jun 06, 2008 at 12:56:48AM +0200, Nikolaj Thygesen wrote:
 Hi,
 
I hope this is the right list to ask this question. I recently 
 commited a new port, and received two messages from ports. The first 
 one noted that a person had assigned the port to himself, and the second 
 mail simply stated that the PR went from open to closed due to 
 feedback timeout. I reckon this means the port was rejected, but have 
 no clue for what reason. Was I supposed to supply any kind of feedback 
 somewhere??
 
 
br - Nikolaj
 
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to [EMAIL PROTECTED]
I have put up ports that are new and have not heard anything myself but it 
sounds like they were waiting for someone to give feedback on your port. 


pgpYu74DMgZ04.pgp
Description: PGP signature

Re: Commiting new ports

[Sahil Tandon]

Wesley Shields [EMAIL PROTECTED] wrote:

 On Fri, Jun 06, 2008 at 12:56:48AM +0200, Nikolaj Thygesen wrote:
  Hi,
  
  I hope this is the right list to ask this question. I recently 
  commited a new port, and received two messages from ports. The first 
  one noted that a person had assigned the port to himself, and the second 
  mail simply stated that the PR went from open to closed due to 
  feedback timeout. I reckon this means the port was rejected, but have 
  no clue for what reason. Was I supposed to supply any kind of feedback 
  somewhere??
 
 I would suggest following up with the person who closed the PR (which I
 assume was the same person it was assigned to).  There is a good chance
 the feedback request was not seen by you for any number of reasons.
 Lastly, the feedback being requested should also be in the audit-trail
 of the PR if possible, so you may be able to look there if you have not
 already.
 
 Without more information I'm afraid we can't help you further.  We would
 need, at a minimum, the PR number to follow up.

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/123239

Perhaps Martin sought feedback from Nikolaj via email and did not receive a 
reply.
   
-- 
Sahil Tandon [EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

NEW PORTS

[Diego Rocha]

Submitter-Id:  current-users
Originator:diego rocha
Organization:
Confidential:  no
Synopsis:  [NEW PORT]sysutils/pkgsearch : find your packages
Severity:  non-critical
Priority:  low
Category:  ports
Class: change-request
Release:   FreeBSD 6.2-RELEASE i386
Environment:
System: FreeBSD localhost.localdomain 6.2-RELEASE FreeBSD 6.2-RELEASE
#0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]
alo.edu:/usr/obj/usr/src/sys/SMP i386



Description:
 pkgsearch find packages in ports in any place from your
computer , and find also packages
 installeds in your system, pkgsearch use c++, boost and
sqlite3 for search packages more
 fast and is compiled with cmake

How-To-Repeat:

Fix:
# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering sh file.  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#   pkgsearch/Makefile
#   pkgsearch/distinfo
#   pkgsearch/files
#   pkgsearch/pkg-descr
#   pkgsearch/pkg-plist
#
echo x - pkgsearch/Makefile
sed 's/^X//' pkgsearch/Makefile  'END-of-pkgsearch/Makefile'
X# New ports collection makefile for: Diego_Rocha
X# Date created:14 September 2007
X# Whom:Diego_Rocha
X#
X# $FreeBSD$
X#
X
XPORTNAME=  pkgsearch
XPORTVERSION=   1.0
XCATEGORIES=sysutils
XMASTER_SITES=  http://dl.sharesource.org/${PORTNAME}/ \
X   http://andsux.homeip.net/~diego/stable/
X
XMAINTAINER=[EMAIL PROTECTED]
XCOMMENT=   Find your packages in ports and installeds packages
X
XBUILD_DEPENDS= cmake:${PORTSDIR}/devel/cmake \
X   gzip:${PORTSDIR}/archivers/gzip
X
XLIB_DEPENDS=   sqlite3:${PORTSDIR}/databases/sqlite3 \
X   boost_filesystem:${PORTSDIR}/devel/boost
X
XWRKSRC=${WRKDIR}/${DISTNAME}-build
XCMAKE_ARGS=-DDIRBUILD:STRING=${WRKDIR}/${DISTNAME}/
X
Xpost-extract:
X   ${MKDIR} ${WRKSRC}
X
Xdo-configure:
X   @(cd ${WRKSRC}; \
X   ${LOCALBASE}/bin/cmake ${CMAKE_ARGS} ../${DISTNAME})
X
X.include bsd.port.mk
END-of-pkgsearch/Makefile
echo x - pkgsearch/distinfo
sed 's/^X//' pkgsearch/distinfo  'END-of-pkgsearch/distinfo'
XMD5 (pkgsearch-1.0.tar.gz) = e55dfe0f99ccb2370451fe88309ebab8
XSHA256 (pkgsearch-1.0.tar.gz) =
348c6d2f87eafa26740567fd9b0a930810e3e18e0edc3a36992d30e79b8fd428
XSIZE (pkgsearch-1.0.tar.gz) = 9949
END-of-pkgsearch/distinfo
echo c - pkgsearch/files
mkdir -p pkgsearch/files  /dev/null 21
echo x - pkgsearch/pkg-descr
sed 's/^X//' pkgsearch/pkg-descr  'END-of-pkgsearch/pkg-descr'
Xpkgsearch find packages in ports, pkgsrc, slackports and others,
Xin any place from your computer, and find also packages installed
Xin your system ! pkgsearch use c++, boost and sqlite3 for search
Xpackages more fast, and is compiled with cmake. enjoy ;)
X
XWWW: http://sharesource.org/project/pkgsearch
END-of-pkgsearch/pkg-descr
echo x - pkgsearch/pkg-plist
sed 's/^X//' pkgsearch/pkg-plist  'END-of-pkgsearch/pkg-plist'
Xsbin/pkgsearch
Xetc/pkgsearch
Xman/man1/pkgsearch.1.gz
Xman/man5/pkgsearch.conf.5.gz
END-of-pkgsearch/pkg-plist
exit
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

NEW PORTS

[Diego Rocha]

Submitter-Id:  current-users
Originator:Diego Rocha [EMAIL PROTECTED]
Organization:
Confidential:  no
Synopsis:  [NEW PORT]sysutils/pkgsearch : find your packages
Severity:  non-critical
Priority:  low
Category:  ports
Class: change-request
Release:   FreeBSD 6.2-RELEASE i386
Environment:
System: FreeBSD localhost.localdomain 6.2-RELEASE FreeBSD 6.2-RELEASE
#0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]
alo.edu:/usr/obj/usr/src/sys/SMP i386



Description:
 pkgsearch find packages in ports in any place from your
computer , and find also packages
 installeds in your system, pkgsearch use c++, boost and
sqlite3 for search packages more
 fast and is compiled with cmake

How-To-Repeat:

Fix:
# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering sh file.  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#   pkgsearch/Makefile
#   pkgsearch/distinfo
#   pkgsearch/files
#   pkgsearch/pkg-descr
#   pkgsearch/pkg-plist
#
echo x - pkgsearch/Makefile
sed 's/^X//' pkgsearch/Makefile  'END-of-pkgsearch/Makefile'
X# New ports collection makefile for: Diego_Rocha
X# Date created:14 September 2007
X# Whom:Diego_Rocha
X#
X# $FreeBSD$
X#
X
XPORTNAME=  pkgsearch
XPORTVERSION=   1.0
XCATEGORIES=sysutils
XMASTER_SITES=  http://dl.sharesource.org/${PORTNAME}/ \
X   http://andsux.homeip.net/~diego/stable/
X
XMAINTAINER=[EMAIL PROTECTED]
XCOMMENT=   Find your packages in ports and installeds packages
X
XBUILD_DEPENDS= cmake:${PORTSDIR}/devel/cmake \
X   gzip:${PORTSDIR}/archivers/gzip
X
XLIB_DEPENDS=   sqlite3:${PORTSDIR}/databases/sqlite3 \
X   boost_filesystem:${PORTSDIR}/devel/boost
X
XWRKSRC=${WRKDIR}/${DISTNAME}-build
XCMAKE_ARGS=-DDIRBUILD:STRING=${WRKDIR}/${DISTNAME}/
X
Xpost-extract:
X   ${MKDIR} ${WRKSRC}
X
Xdo-configure:
X   @(cd ${WRKSRC}; \
X   ${LOCALBASE}/bin/cmake ${CMAKE_ARGS} ../${DISTNAME})
X
X.include bsd.port.mk
END-of-pkgsearch/Makefile
echo x - pkgsearch/distinfo
sed 's/^X//' pkgsearch/distinfo  'END-of-pkgsearch/distinfo'
XMD5 (pkgsearch-1.0.tar.gz) = e55dfe0f99ccb2370451fe88309ebab8
XSHA256 (pkgsearch-1.0.tar.gz) =
348c6d2f87eafa26740567fd9b0a930810e3e18e0edc3a36992d30e79b8fd428
XSIZE (pkgsearch-1.0.tar.gz) = 9949
END-of-pkgsearch/distinfo
echo c - pkgsearch/files
mkdir -p pkgsearch/files  /dev/null 21
echo x - pkgsearch/pkg-descr
sed 's/^X//' pkgsearch/pkg-descr  'END-of-pkgsearch/pkg-descr'
Xpkgsearch find packages in ports, pkgsrc, slackports and others,
Xin any place from your computer, and find also packages installed
Xin your system ! pkgsearch use c++, boost and sqlite3 for search
Xpackages more fast, and is compiled with cmake. enjoy ;)
X
XWWW: http://sharesource.org/project/pkgsearch
END-of-pkgsearch/pkg-descr
echo x - pkgsearch/pkg-plist
sed 's/^X//' pkgsearch/pkg-plist  'END-of-pkgsearch/pkg-plist'
Xsbin/pkgsearch
Xetc/pkgsearch
Xman/man1/pkgsearch.1.gz
Xman/man5/pkgsearch.conf.5.gz
END-of-pkgsearch/pkg-plist
exit
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Policy on new ports

[Atz-Soft]

Hello!

I'd be interested in the policy about new ports in the following situation:

The program has the GNU General Public License as published by the Free
Software Foundation; either version 2 of the License, or (at your option)
any later version.
The program is not in the FreeBSD ports system but can be compiled on
FreeBSD without problems with approx. 5 commands.
And because of that the author may not want his program in the ports
collection.

So will the program be added even if the author may disagree with that?


Regards,
atz

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

Re: Policy on new ports

[LI Xin]

Atz-Soft wrote:
 Hello!
 
 I'd be interested in the policy about new ports in the following situation:
 
 The program has the GNU General Public License as published by the Free
 Software Foundation; either version 2 of the License, or (at your option)
 any later version.
 The program is not in the FreeBSD ports system but can be compiled on
 FreeBSD without problems with approx. 5 commands.
 And because of that the author may not want his program in the ports
 collection.
 
 So will the program be added even if the author may disagree with that?

My understanding is that the build skeleton (we call it ports) is not
a derived work of the original application and therefore you own the
port itself, and it's up to you to decide whether it can be included in
the ports collection.

Cheers,
-- 
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature

Re: Policy on new ports

[Atz-Soft]

Fabian Keil [EMAIL PROTECTED] wrote:

 Is that an assumption or do you really know someone who
 first uses a free license and then objects to people
 distributing his program in compliance with that license?

Just an assumption. I didn't want to spend time and effort creating a port
and then not be able to add it.

Thanks,
atz

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

Re: Policy on new ports

[Fabian Keil]

Atz-Soft [EMAIL PROTECTED] wrote:

 I'd be interested in the policy about new ports in the following situation:
 
 The program has the GNU General Public License as published by the Free
 Software Foundation; either version 2 of the License, or (at your option)
 any later version.
 The program is not in the FreeBSD ports system but can be compiled on
 FreeBSD without problems with approx. 5 commands.
 And because of that the author may not want his program in the ports
 collection.

Is that an assumption or do you really know someone who
first uses a free license and then objects to people
distributing his program in compliance with that license?

I would assume that most authors are either glad that
someone considers their program worthy enough to create
a port for it, or just don't care.

 So will the program be added even if the author may disagree with that?

Usually the author isn't asked for his opinion, if the license
allows distribution, it's assumed that the author is ok with it.

I don't know if there ever was a situation where the
author of a GPL'ed program asked to remove it from the
ports collection again, but in my opinion such requests
should be ignored. If the author doesn't want distribution
he shouldn't use a license that allows it.

Fabian


signature.asc
Description: PGP signature

Re: Policy on new ports

[Paul Chvostek]

On Wed, Feb 21, 2007 at 12:25:06PM +0100, Atz-Soft wrote:
 
 The program has the GNU General Public License as published by the Free
 Software Foundation; either version 2 of the License, or (at your option)
 any later version.
 The program is not in the FreeBSD ports system but can be compiled on
 FreeBSD without problems with approx. 5 commands.
 And because of that the author may not want his program in the ports
 collection.

If that's the author's reason for not wanting a FreeBSD point, I suspect
he can be safely ignored.

If you want to engage him in further conversation about this, points to
remember (or perhaps to make) are:

1) The port is not the software, it's effectively a database entry
implemented in a Makefile, and the license on the port is completely
independent of the license of the software.  (That said, USING the port
could potentially violate a license if the software wasn't GPL'd.)  In
the absense of a blanket policy that ports in the FreeBSD ports tree are
covered by the same license as FreeBSD, I believe that YOU as the author
of the port determine the license.  (Note: IANAL. I don't even play one
on TV.)

2) The five commands required to compile the software comprise only ONE
requirement addressed by a port.  Others include upgrade management,
security vulnerability tracking and dependencies.  We use the ports
system to address ALL these requirements, not just the compile process.

 So will the program be added even if the author may disagree with that?

The port is not the software.  If the author wants to limit the
availability of the software, he needs to use a license that allows
this.  GPL is not that license.  And the effect of such a license will
be to limit the ACTIVITY of the port, not the existence of it, since the
port is not a derived work.

-- 
  Paul Chvostek [EMAIL PROTECTED]
  Operations / Abuse / Whatever
  it.canada, hosting and development   http://www.it.ca/

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

[HEADSUP] new portmgr recommendation about adding new ports

[Mark Linimon]

Here is the result of a discussion amongst the portmgr members during the
past few weeks, in response to the large number of new ports added to the
Ports Collection in the last few months.

-

Recently we've seen evidence of an increase in the number of ports that
are submitted just because the software is there, and not out of any
underlying need for the port to exist.

When considering a new port, portmgr would like to ask you to please apply
the following criterion:

  New ports should only be submitted by someone who is actually using the
  software and will continue to use the port to maintain the software.

Adding a port of software that you do not personally use, or do not use
within the FreeBSD ports collection (such as an xpi browser extension that
you manage using firefox and not using the Ports Collection), is not a good
tradeoff between adding functionality and adding complexity.

Each additional port requires resources, both machine (from the package
building system) and people (to inspect the results from the package
building system).  This is especially true when you consider that we, as
a team, are all trying to keep ports buildable on on 4 different branches
and 5 different architectures (with increasing interest in arm and powerpc).

Past experience shows that these ports often quickly fall behind as new
versions are released, and when build breakages occur, they do not get
fixed.  In some other cases, some of our contributors try to keep ports
viable by fixes and updating long after their real usefulness has passed,
and that time could be better spent on the more worthwhile ports.

While no one is suggesting that we go the route some projects have with
some kind of 'gateway' process for approving new ports, at some point the
number of ports will simply be too great for our infrastructure (package
building system, sending PRs via email).  Some common sense should help
to keep us from reaching that point.

As a reminder, the Ports Collection already has 198 ports marked BROKEN*,
and 4291 unmaintained ones.  We really don't need to add to these numbers.

To summarize, we simply can't support all the possible applications out
on the Internet, so we need to use common sense to try to keep it down to
a maintainable number.

mcl

(*: on i386-6; the numbers are higher on the other architectures, and -CURRENT)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]