Re: New port, what's next?
On 10/04/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Regards ... autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems The majority of problems I used to have as a port maintainer stemmed from fiddling with plists. I.e. my experience is the opposite, manual plists lead to errors. Autogenerated plists (which I use in most cases, because dynamic ones are against policy) have reduced the amount of mistakes I make tremendously. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: New port, what's next?
On 10/04/2014 23:14, Lars Engels wrote: On Thu, Apr 10, 2014 at 08:37:45PM +0200, John Marino wrote: On 4/10/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems Yes, but 6,000 - 20,000 line plists are unwieldy to say the least. And the danger can be mitigated by the maintainer by reviewing the internal temporary package list, ideally on multiple platforms. Also some plists are really hard to make manually if there are many options or if the plist morphs depending on the combination of options. yes, a safety net is removed with a generated plist but it has it's place. The maintainer just has to be vigilant. Can't we teach the ports system to handle pkg-plist.gz? That would be easy enough. The question is, can svn handle it? -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: New port, what's next?
On Fri, Apr 11, 2014 at 11:14:21AM +0200, Dominic Fandrey wrote: On 10/04/2014 23:14, Lars Engels wrote: On Thu, Apr 10, 2014 at 08:37:45PM +0200, John Marino wrote: On 4/10/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems Yes, but 6,000 - 20,000 line plists are unwieldy to say the least. And the danger can be mitigated by the maintainer by reviewing the internal temporary package list, ideally on multiple platforms. Also some plists are really hard to make manually if there are many options or if the plist morphs depending on the combination of options. yes, a safety net is removed with a generated plist but it has it's place. The maintainer just has to be vigilant. Can't we teach the ports system to handle pkg-plist.gz? That would be easy enough. The question is, can svn handle it? Nope :) regards, Bapt pgpyhKgn5IDkK.pgp Description: PGP signature
Re: New port, what's next?
On Fri, Apr 11, 2014 at 2:13 AM, Dominic Fandrey kamik...@bsdforen.dewrote: On 10/04/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Regards ... autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems The majority of problems I used to have as a port maintainer stemmed from fiddling with plists. I.e. my experience is the opposite, manual plists lead to errors. Autogenerated plists (which I use in most cases, because dynamic ones are against policy) have reduced the amount of mistakes I make tremendously. I find redports is an effective way to check on plists. I found that it was the best way to catch errors, especially on one port that had a many hundred line long plist. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@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 port, what's next?
Hi, I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. www/typo345 and www/typo347 will deprecate and only www/typo3 and www/typo3-LTS shall remain in the ports tree. What's next? Thanks in advance, Helmut --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.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: New port, what's next?
On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: New port, what's next?
Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. In my opinion huge plists should be dynamically generated Tell me more. :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: New port, what's next?
On 4/10/2014 19:44, Helmut Schneider wrote: Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. In my opinion huge plists should be dynamically generated Tell me more. :) http://svnweb.freebsd.org/ports/head/lang/gcc-aux/Makefile?revision=350807view=markup Look at the post-install target for an example how to do this. here's another example: http://svnweb.freebsd.org/ports/head/www/aws/Makefile?revision=349237view=markup 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: New port, what's next?
On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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 Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems regards, Bapt pgpn99DPGuQTq.pgp Description: PGP signature
Re: New port, what's next?
On 4/10/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems Yes, but 6,000 - 20,000 line plists are unwieldy to say the least. And the danger can be mitigated by the maintainer by reviewing the internal temporary package list, ideally on multiple platforms. Also some plists are really hard to make manually if there are many options or if the plist morphs depending on the combination of options. yes, a safety net is removed with a generated plist but it has it's place. The maintainer just has to be vigilant. 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: New port, what's next?
On Thu, Apr 10, 2014 at 08:37:45PM +0200, John Marino wrote: On 4/10/2014 20:28, Baptiste Daroussin wrote: On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: On 10/04/2014 18:53, Helmut Schneider wrote: I created a new port, Typo3-LTS. The tgz contains - Makefile - distinfo - pkg-plist - pkg-descr - a diff from www/typo3 The file has ~150kB so I assume it's to big for a PR. I assume the bulk of that is the pkg-plist. The largest pkg-plist in the ports tree is 4M. In my opinion huge plists should be dynamically generated, but in your case I'd just I'd just temp-host the file somewhere and file a PR with a link and a checksum. Autoplist are harmful! and should be avoided as much as possible, I know python and ruby has it but I m really not happy about that autoplist is dangerous because we have no way to control that what is package is what the maintainer expect to be packaged! therefore we often end up with unoticed problems Yes, but 6,000 - 20,000 line plists are unwieldy to say the least. And the danger can be mitigated by the maintainer by reviewing the internal temporary package list, ideally on multiple platforms. Also some plists are really hard to make manually if there are many options or if the plist morphs depending on the combination of options. yes, a safety net is removed with a generated plist but it has it's place. The maintainer just has to be vigilant. Can't we teach the ports system to handle pkg-plist.gz? pgpVQZOwTagy4.pgp Description: PGP signature
