Re: [HEADS UP] Ports Infrastructure Changes
On Fr, 25.03.2011 at 07:11:42 +0800, Martin Wilke wrote:
On Fri, Mar 25, 2011 at 4:06 AM, Ulrich Spörlein u...@freebsd.org wrote:
On Sat, 19.03.2011 at 09:49:39 +0800, Martin Wilke wrote:
Hey,
as the Ports Collection continue to grow, we have decided to
do some changes to the category layout. The www category, second
largest with over 2000 individual ports, will have three subcategories
spinned out. On the other side, x11-servers category, with only
10 ports, will be folded into regular x11 category.
Why? I can understand you'd like to move the handful of x11-servers into
x11, but what do you gain by splitting www?
The time and repo-churn could probably be spent on something more
constructive than moving ports around.
so can u guys please come back to the review of the ports for the categorie
move?
It would still be nice to know, what you think this move will improve.
Because it will fuck over people who have for example the following in
their make.conf
.if ${.CURDIR:M*/www/apache2*}
WITH_APR_FROM_PORTS=true
WITH_LDAP=true
WITH_AUTHNZ_LDAP=true
.endif
Let alone people who have used the OPTIONS framework and saved their
settings to /var/db/ports/.
So, again, what is gained by that move and how does it offset those
people's inconvenience?
Regards,
Uli
___
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: [HEADS UP] Ports Infrastructure Changes
Doug Barton do...@freebsd.org wrote: This would be a good time to include ports-mgmt/pkg_search into the base system... It would be a better idea to put the pkg_* tools IN the ports tree where they belong. :) Wouldn't this lead to a chicken-egg problem for those who use packages? How would one go about installing the package installer? ___ 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: [HEADS UP] Ports Infrastructure Changes
On Wed, 23 Mar 2011 18:34:35 -, Olivier Smedts oliv...@gid0.org wrote: 2011/3/23 Doug Barton do...@freebsd.org: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera Or find /usr/ports -maxdepth 2 -name opera Slower than make search but faster than building an INDEX file before make search ! So, considering it is so easy to find where the port it, does it really matter where it goes ? I would have thought that the only structure that won't result in potential restructuring all of the time is one that doesn't depend on separation by package class. So something like: All/o/opera you can then build category based directories with symlinks to the main location based on what categories the port reports that it is in, but these directories are really just helpers for find ports. I'm sure that something like this has been mentioned before. But I don't see what else is going to stop the categorization issue popping up all of the time. -- Using Opera's revolutionary email client: http://www.opera.com/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: [HEADS UP] Ports Infrastructure Changes
you can then build category based directories with symlinks to the main location based on what categories My ports-mgmt/symports does something like this. It builds a full directory tree of symlinks for the secondary categories. I'm sure that something like this has been mentioned before. But I don't see what else is going to stop the categorization issue popping up all of the time. If we alphabetized the ports then there would be constant conversation about how whether or not we should categorize them. -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
On Thu, Mar 24, 2011 at 10:38:48AM -0500, Eitan Adler thus spake: you can then build category based directories with symlinks to the main location based on what categories My ports-mgmt/symports does something like this. It builds a full directory tree of symlinks for the secondary categories. I'm sure that something like this has been mentioned before. But I don't see what else is going to stop the categorization issue popping up all of the time. If we alphabetized the ports then there would be constant conversation about how whether or not we should categorize them. -- Eitan Adler When this change goes in, it may be a good idea to commit a documentation change, as well, that cleans up and adds the new categories here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categories.html -jgh -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ 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: [HEADS UP] Ports Infrastructure Changes
On Thu, Mar 24, 2011 at 09:23:22AM -0700, Jason Helfman wrote: On Thu, Mar 24, 2011 at 10:38:48AM -0500, Eitan Adler thus spake: you can then build category based directories with symlinks to the main location based on what categories My ports-mgmt/symports does something like this. It builds a full directory tree of symlinks for the secondary categories. I'm sure that something like this has been mentioned before. But I don't see what else is going to stop the categorization issue popping up all of the time. If we alphabetized the ports then there would be constant conversation about how whether or not we should categorize them. -- Eitan Adler When this change goes in, it may be a good idea to commit a documentation change, as well, that cleans up and adds the new categories here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categories.html I'm against this change. I've never had any problems with the way ports are categorised. Also, refuse file is arranged in categories, so I can, and often do, remove the whole categories of ports from my /usr/ports, e.g. languages which I don't speak, or java, or whatever. Spending time and energy on rearranging everything in alphabetic order is a waste of time and will not help me a bit. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
On Thu, Mar 24, 2011 at 04:41:33PM +, Anton Shterenlikht thus spake: On Thu, Mar 24, 2011 at 09:23:22AM -0700, Jason Helfman wrote: On Thu, Mar 24, 2011 at 10:38:48AM -0500, Eitan Adler thus spake: you can then build category based directories with symlinks to the main location based on what categories My ports-mgmt/symports does something like this. It builds a full directory tree of symlinks for the secondary categories. I'm sure that something like this has been mentioned before. But I don't see what else is going to stop the categorization issue popping up all of the time. If we alphabetized the ports then there would be constant conversation about how whether or not we should categorize them. -- Eitan Adler When this change goes in, it may be a good idea to commit a documentation change, as well, that cleans up and adds the new categories here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categories.html I'm against this change. I've never had any problems with the way ports are categorised. Also, refuse file is arranged in categories, so I can, and often do, remove the whole categories of ports from my /usr/ports, e.g. languages which I don't speak, or java, or whatever. Spending time and energy on rearranging everything in alphabetic order is a waste of time and will not help me a bit. I was referring to the change of the original idea of this thread regarding the splitting up of www, respectively. This thread has dealt with a plethora of changes. -jgh ___ 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: [HEADS UP] Ports Infrastructure Changes
When this change goes in, it may be a good idea to commit a documentation change, as well, that cleans up and adds the new categories here: Is the attached patch sufficient? -- Eitan Adler www-category-porters-handbook.diff Description: Binary data ___ 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: [HEADS UP] Ports Infrastructure Changes
On Thu, 24 Mar 2011 11:38, lists@ wrote: you can then build category based directories with symlinks to the main location based on what categories My ports-mgmt/symports does something like this. It builds a full directory tree of symlinks for the secondary categories. I'm sure that something like this has been mentioned before. But I don't see what else is going to stop the categorization issue popping up all of the time. If we alphabetized the ports then there would be constant conversation about how whether or not we should categorize them. I agree with that but wouldn't it be great if there was something in place that would be extensible beyond a few thousand ports without having to think about what the contents of that directory would be ? If we stopped imposing upon the names of projects like Perl with p5- or python with py- and put them in their respective alphabetic category ? If you already knew what you were looking for and you knew the structure then their is no need to search ( cd /usr/ports/pool/A-Z/portname ). A few thoughts I had to go along with this the other day when I mentioned it in ##freebsd before it was brought up here, but laced out in a tree format where I can better visually explain it than put it in words as a rough draft. I envision the tag-files directory below as a community effort of the Wikipedia kind that would lift the effort off of the committer's backs and promote more of an open involvement as a whole to edit them. This is where I seen the use of a DVCS like Mercurial come into play because if you divide it up the tree properly into separate repo's then cloning and distribution and community involvement of those repo's becomes a benefit. A referral access system along with key access, (*). ./ports |-- COPYRIGHT |-- Changelog/ | |-- ABI | |-- DELETED | |-- DEPRECATED | |-- OBSOLETED | |-- OPTIONS | `-- UPDATING |-- Distfiles/ |-- GIDs |-- INDEX-8 |-- KNOBS |-- Mgmt/ | |-- pkg_cutleaves/ | |-- portmaster/ | |-- portupgrade/ | `-- tinderbox/ |-- Mk/ |-- Packages/ |-- Tagfiles/ | |-- categories/ | | |-- devel-all | | |-- ftp-all | | |-- www-client-all | | |-- www-server-all | | `-- www-webapp-all | |-- community/ | | `-- custom-server-tag1 | `-- installs/ | |-- desktop-install-kde4.2 | `-- lamp-install |-- Templates/ |-- Tools/ |-- UIDs `-- pool/ |-- a/ |-- b/ |-- c/ | `-- clang/ |-- d/ |-- e/ |-- f/ | `-- firefox/ |-- g/ |-- h/ |-- l/ | `-- llvm-devel/ |-- libc/ |-- libh/ |-- p/ | `-- perl5.10/ |-- t/ `-- z/ Just some cents for the mail-bank. It works as it is now, if you are happy running through every once in a while and re-categorizing things and re-judging whether something is supposed to or should be in a category then sobeit, ultimately it doesn't stop the software from working on the other end and the work is still very much appreciated either way. -- Regards, J. Hellenthal (0x89D8547E) JJH48-ARIN ___ 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: [HEADS UP] Ports Infrastructure Changes
On Thu, Mar 24, 2011 at 01:12:49PM -0500, Eitan Adler thus spake: When this change goes in, it may be a good idea to commit a documentation change, as well, that cleans up and adds the new categories here: Is the attached patch sufficient? -- Eitan Adler Looks good. I was going to create one, myself, but didn't have time to investigate if other categories were introduced, or removed that require adjustment. I took a look though against /usr/ports and compared the categories, and there is nothing that requires any changes from the category naming point-of-view. I only looked at actual categories, though, and didn't compare meta-categories. -jgh -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ 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: [HEADS UP] Ports Infrastructure Changes
On 03/24/2011 01:22, per...@pluto.rain.com wrote: Doug Bartondo...@freebsd.org wrote: This would be a good time to include ports-mgmt/pkg_search into the base system... It would be a better idea to put the pkg_* tools IN the ports tree where they belong. :) Wouldn't this lead to a chicken-egg problem for those who use packages? How would one go about installing the package installer? 1) The system installer installs the package that contains the latest version of the pkg_* tools by default. 2) Have a stub program in the base whose only purpose is to download and install the latest version of the pkg_* tools. The benefits of this are that we can introduce new features to the pkg_* tools very quickly, rather than with a 3 year (or more) lead time like we do now. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go 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: [HEADS UP] Ports Infrastructure Changes
On Sat, 19.03.2011 at 09:49:39 +0800, Martin Wilke wrote: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Why? I can understand you'd like to move the handful of x11-servers into x11, but what do you gain by splitting www? The time and repo-churn could probably be spent on something more constructive than moving ports around. Uli -- Hierarchies don't work! ___ 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: [HEADS UP] Ports Infrastructure Changes
so can u guys please come back to the review of the ports for the categorie move? On Fri, Mar 25, 2011 at 4:06 AM, Ulrich Spörlein u...@freebsd.org wrote: On Sat, 19.03.2011 at 09:49:39 +0800, Martin Wilke wrote: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Why? I can understand you'd like to move the handful of x11-servers into x11, but what do you gain by splitting www? The time and repo-churn could probably be spent on something more constructive than moving ports around. Uli -- Hierarchies don't work! -- +-oOO--(_)--OOo-+ With best Regards, Martin Wilke (miwi_(at)_FreeBSD.org) Mess with the Best, Die like the Rest ___ 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: [HEADS UP] Ports Infrastructure Changes
On Sun, 20 Mar 2011 07:26:45 -, Zhihao Yuan lich...@gmail.com wrote: On Sat, Mar 19, 2011 at 5:29 PM, Henk van Oers h...@signature.nl wrote: From: Pav Lucistnik p...@freebsd.org Matthias Andree pí¹e v so 19. 03. 2011 v 09:52 +0100: [...] Where do you see the dividing line between web apps on one hand and on the other hand http servers ... everything related to apache? IOW, how do I decide if I put a new port into www-webapps or into www-servers for its primary category? Basically, everything that serves network is server and everything that generates pages on these servers is webapp. So: why is p5-Mojolicious in webapp, it serves network (main deployment). And it's a client too... Not just p5-Mojolicious. Many webapps can be web servers, like Flask. Even some unrelated packages can be www servers, like python, with SimpleHTTPServer. And some www-clients can also be www-servers. For example, opera. It's a client, server, email client, HTML-editor. You can't just *separate* things into clients, servers, apps, and misc. I would say that although it is correct to say that something like Opera is all of those things you should think about the main way in which the application is perceived. If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file, because I'd have no idea where else it might be. I shouldn't need to know its full in depth feature set just so that I can find it to install it. And also, during the development of the HTML5, there will be more and more www-client ports can be used as servers, by using web socket. The border of clients and servers will become fuzzy. We should not used a C/S model to sort these ports. That's why I suggest that to create a www-devel branch - you can determined what a software is mainly designed for, but you can not always determined what a software can be used as. ___ 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: [HEADS UP] Ports Infrastructure Changes
On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go 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: [HEADS UP] Ports Infrastructure Changes
2011/3/23 Doug Barton do...@freebsd.org: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera Or find /usr/ports -maxdepth 2 -name opera Slower than make search but faster than building an INDEX file before make search ! -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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: [HEADS UP] Ports Infrastructure Changes
On 03/23/2011 11:34, Olivier Smedts wrote: 2011/3/23 Doug Bartondo...@freebsd.org: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera Or find /usr/ports -maxdepth 2 -name opera Slower than make search but faster than building an INDEX file before make search ! Who said anything about building an INDEX? :) If you use portsnap to update your ports tree it comes along for free. If not, then 'make fetchindex' will do the trick for you. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go 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: [HEADS UP] Ports Infrastructure Changes
2011/3/23 Doug Barton do...@freebsd.org: On 03/23/2011 11:34, Olivier Smedts wrote: 2011/3/23 Doug Bartondo...@freebsd.org: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera Or find /usr/ports -maxdepth 2 -name opera Slower than make search but faster than building an INDEX file before make search ! Who said anything about building an INDEX? :) If you use portsnap to update your ports tree it comes along for free. If not, then 'make fetchindex' will do the trick for you. Will it take care of my INDEX-9 file for FreeBSD 9-CURRENT with the following setting I just appended to /etc/portsnap.conf ? # tail -n 1 /etc/portsnap.conf INDEX INDEX-9 DESCRIBE.9 I'm not sure (no irony, really asking), because portsnap update -I does not modify /usr/ports/INDEX-9. Maybe DESCRIBE.9 is not distributed on the portsnap servers. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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: [HEADS UP] Ports Infrastructure Changes
Doug Barton wrote: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera This would be a good time to include ports-mgmt/pkg_search into the base system... ___ 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: [HEADS UP] Ports Infrastructure Changes
On 03/23/2011 12:04, Helmut Schneider wrote: Doug Barton wrote: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera This would be a good time to include ports-mgmt/pkg_search into the base system... It would be a better idea to put the pkg_* tools IN the ports tree where they belong. :) -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go 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: [HEADS UP] Ports Infrastructure Changes
On Wed, 23 Mar 2011, Olivier Smedts wrote: 2011/3/23 Doug Barton do...@freebsd.org: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera Or find /usr/ports -maxdepth 2 -name opera Slower than make search but faster than building an INDEX file before make search ! % whereis opera opera: /usr/ports/www/opera Granted, it doesn't always work. ___ 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: [HEADS UP] Ports Infrastructure Changes
2011/3/23 Olivier Smedts oliv...@gid0.org: 2011/3/23 Doug Barton do...@freebsd.org: On 03/23/2011 11:34, Olivier Smedts wrote: 2011/3/23 Doug Bartondo...@freebsd.org: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera Or find /usr/ports -maxdepth 2 -name opera Slower than make search but faster than building an INDEX file before make search ! Who said anything about building an INDEX? :) If you use portsnap to update your ports tree it comes along for free. If not, then 'make fetchindex' will do the trick for you. Will it take care of my INDEX-9 file for FreeBSD 9-CURRENT with the following setting I just appended to /etc/portsnap.conf ? # tail -n 1 /etc/portsnap.conf INDEX INDEX-9 DESCRIBE.9 I've got my answer, now that there's a new snapshot on portsnap servers. # portsnap fetch update [...] Building new INDEX files... DESCRIBE.9 not provided by portsnap server; INDEX-9 not being generated. I'm not sure (no irony, really asking), because portsnap update -I does not modify /usr/ports/INDEX-9. Maybe DESCRIBE.9 is not distributed on the portsnap servers. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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: [HEADS UP] Ports Infrastructure Changes
On Wed, Mar 23, 2011 at 07:04:26PM +, Helmut Schneider wrote: Doug Barton wrote: On 03/23/2011 03:48, Peter Jeffery wrote: If I was looking for the Opera port, I'd look in www-clients and if it wasn't in there then the next thing that I would be doing is hand searching the INDEX file cd /usr/ports/ make search name=opera This would be a good time to include ports-mgmt/pkg_search into the base system... No, please keep the base system as small as possible. ports(7) answered most, if not all, my questions. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
Henk van Oers píše v so 19. 03. 2011 v 23:29 +0100: From: Pav Lucistnik p...@freebsd.org Matthias Andree pí¹e v so 19. 03. 2011 v 09:52 +0100: [...] Where do you see the dividing line between web apps on one hand and on the other hand http servers ... everything related to apache? IOW, how do I decide if I put a new port into www-webapps or into www-servers for its primary category? Basically, everything that serves network is server and everything that generates pages on these servers is webapp. So: why is p5-Mojolicious in webapp, it serves network (main deployment). And it's a client too... COMMENT=A high level MVC web framework written in Perl Screams webapp to me, but, I don't know every existing software in detail so maybe I'm wrong here. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org In the beginning was the word, and the word was content-type: text/plain signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
On 03/19/2011 11:52 PM, Zhihao Yuan wrote: C/S model can not clarify the developing web technology these years. +1 ___ 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: [HEADS UP] Ports Infrastructure Changes
On Sat, Mar 19, 2011 at 5:29 PM, Henk van Oers h...@signature.nl wrote: From: Pav Lucistnik p...@freebsd.org Matthias Andree pí¹e v so 19. 03. 2011 v 09:52 +0100: [...] Where do you see the dividing line between web apps on one hand and on the other hand http servers ... everything related to apache? IOW, how do I decide if I put a new port into www-webapps or into www-servers for its primary category? Basically, everything that serves network is server and everything that generates pages on these servers is webapp. So: why is p5-Mojolicious in webapp, it serves network (main deployment). And it's a client too... Not just p5-Mojolicious. Many webapps can be web servers, like Flask. Even some unrelated packages can be www servers, like python, with SimpleHTTPServer. And some www-clients can also be www-servers. For example, opera. It's a client, server, email client, HTML-editor. You can't just *separate* things into clients, servers, apps, and misc. And also, during the development of the HTML5, there will be more and more www-client ports can be used as servers, by using web socket. The border of clients and servers will become fuzzy. We should not used a C/S model to sort these ports. That's why I suggest that to create a www-devel branch - you can determined what a software is mainly designed for, but you can not always determined what a software can be used as. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
devel category is the largest one, how about divide it into : devel devel-perl devel-python wen 2011/3/19 Martin Wilke m...@freebsd.org: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache www-webapps - web apps, frameworks, libraries www (rest, not moved) - html editors, authoring tools, search engines .. http://people.freebsd.org/~miwi/cat/www-client.txt http://people.freebsd.org/~miwi/cat/www-server.txt http://people.freebsd.org/~miwi/cat/www-webapps.txt http://people.freebsd.org/~miwi/cat/www.txt - Martin on behalf of portmgr ___ 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: [HEADS UP] Ports Infrastructure Changes
On Sat, Mar 19, 2011 at 04:34:17PM +0800, wen heping wrote: devel category is the largest one, how about divide it into : devel devel-perl devel-python My own view is that naming the categories by language (e.g. java) is not a good idea. I'd rather divide things up by what they do, rather than what they're written in. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
Philip M. Gollucci píše v so 19. 03. 2011 v 00:51 -0400: If might be useful to coordinate this with the default switch from 1.3 No. Let's keep things simple, one thing at a time. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org The use of the lavatory is restricted to the train's cat. signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
Alex Dupre píše v so 19. 03. 2011 v 08:52 +0100: Martin Wilke ha scritto: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache www-webapps - web apps, frameworks, libraries www (rest, not moved) - html editors, authoring tools, search engines .. I was wondering where you put httpcore and httpclient, two java libraries. Even if they are not webapp, from this categorization I'd say they should go there, but I found one in www and one in www-clients. Both will be moved to -clients, thanks. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org A mouse is a device used to point at the xterm you want to type in. signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
devel category is the largest one, how about divide it into : devel devel-perl devel-python wen Is that not partially why we have the virtual categories to provide language divisions (not to mention port name prefixes)? I think were devel to be split 'broad' functionality would be the best and most useful (although harder to do than language) way of splitting things down. Regards Eric ___ 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: [HEADS UP] Ports Infrastructure Changes
Am 19.03.2011 02:49, schrieb Martin Wilke: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache www-webapps - web apps, frameworks, libraries Where do you see the dividing line between web apps on one hand and on the other hand http servers ... everything related to apache? IOW, how do I decide if I put a new port into www-webapps or into www-servers for its primary category? ___ 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: [HEADS UP] Ports Infrastructure Changes
Martin Wilke wrote: [...] www-servers - http servers, proxy servers, everything related to apache www-webapps - web apps, frameworks, libraries www (rest, not moved) - html editors, authoring tools, search engines .. http://people.freebsd.org/~miwi/cat/www-client.txt http://people.freebsd.org/~miwi/cat/www-server.txt http://people.freebsd.org/~miwi/cat/www-webapps.txt http://people.freebsd.org/~miwi/cat/www.txt Maybe I misunderstand something, but where is Apache or Lighttpd server? I can't find them on the www-server list or www. Miroslav Lachman ___ 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: [HEADS UP] Ports Infrastructure Changes
Miroslav Lachman ha scritto: Maybe I misunderstand something, but where is Apache or Lighttpd server? I can't find them on the www-server list or www. Good catch, they aren't in any category :-) but should be in www-server. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
Pav Lucistnik ha scritto: I was wondering where you put httpcore and httpclient, two java libraries. Even if they are not webapp, from this categorization I'd say they should go there, but I found one in www and one in www-clients. Both will be moved to -clients, thanks. So -clients is the container for client libraries, too? And which libraries goes into -webapp? -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
On 3/19/2011 6:09 AM, Pav Lucistnik wrote: Philip M. Gollucci píše v so 19. 03. 2011 v 00:51 -0400: If might be useful to coordinate this with the default switch from 1.3 No. Let's keep things simple, one thing at a time. Okay w/ me. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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: [HEADS UP] Ports Infrastructure Changes
Alex Dupre píše v so 19. 03. 2011 v 14:29 +0100: Pav Lucistnik ha scritto: I was wondering where you put httpcore and httpclient, two java libraries. Even if they are not webapp, from this categorization I'd say they should go there, but I found one in www and one in www-clients. Both will be moved to -clients, thanks. So -clients is the container for client libraries, too? And which libraries goes into -webapp? Yes, client libraries go to -clients, SOAP/webservice/page slurpers go to -clients. Various frameworks, modules, and libraries used in these frameworks, ie stuff running on the server, goes to -webapps. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org Quantum physics was developed in the 1930's, as a result of a bet between Albert Einstein and Niels Bohr, to see who could come up with the most ridiculous theory and still have it published. signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
2011/3/19 Michal Varga varga.mic...@gmail.com: On Sat, 2011-03-19 at 09:49 +0800, Martin Wilke wrote: Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: [...] www-webapps - web apps, frameworks, libraries Just a quick thought to the 'discuss' part: Is this (above) really the best name possible? I mean world wide web-webapps sounds kind of redundant. OK, this is a bikeshed discussion, but I agree here. www-apps would be more appropriate. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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: [HEADS UP] Ports Infrastructure Changes
On Sat 19 Mar 2011 at 12:18:42 PDT Olivier Smedts wrote: 2011/3/19 Michal Varga varga.mic...@gmail.com: On Sat, 2011-03-19 at 09:49 +0800, Martin Wilke wrote: Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: [...] www-webapps - web apps, frameworks, libraries Just a quick thought to the 'discuss' part: Is this (above) really the best name possible? I mean world wide web-webapps sounds kind of redundant. OK, this is a bikeshed discussion, but I agree here. www-apps would be more appropriate. Well, on behalf of the blue bikeshed, I'd like to point out that www-apps isn't specific enough to exclude all the things that are going into the other www- categories. How about www-serverapps? ___ 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: [HEADS UP] Ports Infrastructure Changes
Alex Dupre píše v so 19. 03. 2011 v 14:24 +0100:
Miroslav Lachman ha scritto:
Maybe I misunderstand something, but where is Apache or Lighttpd server?
I can't find them on the www-server list or www.
Good catch, they aren't in any category :-) but should be in www-server.
Good God, they are really missing. Embarassing .. :)
They go to www-servers, of course.
--
--
Pav Lucistnik p...@oook.cz
p...@freebsd.org
An arrow (+0,+0) {@f0} finds a mark. It dies.
signature.asc
Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
Thomas Sandford píše v so 19. 03. 2011 v 14:12 +: On 19/03/2011 01:49, Martin Wilke wrote: as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. ... Whilst we are at it, is now the time to create a voip or telephony category? Generally yes, this is one possibility. Another nice category would be xml. PS libvorbis is not voip-specific and should stay in audio. -- -- Pav Lucistnik p...@oook.cz p...@freebsd.org 42.7 percent of all statistics are made up on the spot. signature.asc Description: This is a digitally signed message part
Re: [HEADS UP] Ports Infrastructure Changes
From: Pav Lucistnik p...@freebsd.org Matthias Andree pí¹e v so 19. 03. 2011 v 09:52 +0100: [...] Where do you see the dividing line between web apps on one hand and on the other hand http servers ... everything related to apache? IOW, how do I decide if I put a new port into www-webapps or into www-servers for its primary category? Basically, everything that serves network is server and everything that generates pages on these servers is webapp. So: why is p5-Mojolicious in webapp, it serves network (main deployment). And it's a client too... ___ 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: [HEADS UP] Ports Infrastructure Changes
On Sat, Mar 19, 2011 at 5:29 PM, Henk van Oers h...@signature.nl wrote: From: Pav Lucistnik p...@freebsd.org Matthias Andree pí¹e v so 19. 03. 2011 v 09:52 +0100: [...] Where do you see the dividing line between web apps on one hand and on the other hand http servers ... everything related to apache? IOW, how do I decide if I put a new port into www-webapps or into www-servers for its primary category? Basically, everything that serves network is server and everything that generates pages on these servers is webapp. So: why is p5-Mojolicious in webapp, it serves network (main deployment). And it's a client too... My suggestion: separate www into www and www-devel. C/S model can not clarify the developing web technology these years. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
On Sat, Mar 19, 2011 at 09:49:39AM +0800, Martin Wilke wrote: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache www-webapps - web apps, frameworks, libraries www (rest, not moved) - html editors, authoring tools, search engines .. Shouldn't we move html editors to ports/editors? pgpV9XneXJQzr.pgp Description: PGP signature
Re: [HEADS UP] Ports Infrastructure Changes
www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache www-webapps - web apps, frameworks, libraries www (rest, not moved) - html editors, authoring tools, search engines .. IMHO html editors should go into the editors/ category. While we are on the subject of moving things around I'd like to see x11/ split out into their appropriate categories. Things like x11/xeyes should go into games/ and x11/xscreensaver into security/ The general x11/ category could be used for infrastructure and servers (the libs and the current -servers category) -- Eitan Adler ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
On 3/19/2011 8:48 PM, Eitan Adler wrote: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache www-webapps - web apps, frameworks, libraries www (rest, not moved) - html editors, authoring tools, search engines .. IMHO html editors should go into the editors/ category. While we are on the subject of moving things around I'd like to see x11/ split out into their appropriate categories. Things like x11/xeyes should go into games/ and x11/xscreensaver into security/ The general x11/ category could be used for infrastructure and servers (the libs and the current -servers category) I tend to agree with Eitan here. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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: [HEADS UP] Ports Infrastructure Changes
On Sat, 2011-03-19 at 09:49 +0800, Martin Wilke wrote: Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: [...] www-webapps - web apps, frameworks, libraries Just a quick thought to the 'discuss' part: Is this (above) really the best name possible? I mean world wide web-webapps sounds kind of redundant. m. -- Michal Varga, Stonehenge (Gmail account) ___ 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: [HEADS UP] Ports Infrastructure Changes
On Fri, Mar 18, 2011 at 9:32 PM, Michal Varga varga.mic...@gmail.com wrote: On Sat, 2011-03-19 at 09:49 +0800, Martin Wilke wrote: Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: [...] www-webapps - web apps, frameworks, libraries Just a quick thought to the 'discuss' part: Is this (above) really the best name possible? I mean world wide web-webapps sounds kind of redundant. m. www-devel may be preferred, since www-webapps contains the web frameworks, libs. or may be devel-www :) -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org -- Zhihao Yuan The best way to predict the future is to invent it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] Ports Infrastructure Changes
On 3/18/2011 9:49 PM, Martin Wilke wrote: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache Good idea or bad idea, it doesn't really matter. I actually kind of like it. More importantly, you'll need to update Mk/bsd.apache.mk regarding APACHE_PORT. And every end-user will need to update /etc/make.conf to reflect this too. If might be useful to coordinate this with the default switch from 1.3 to 2.2 b/c then supposedly most people who are using 2.2 can simply remove then line. And the fewer, still needing 1.3 will need to add one anyway. Food to chew on.. -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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: [HEADS UP] Ports Infrastructure Changes
On 3/18/2011 9:49 PM, Martin Wilke wrote: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache How did you generate this list ? - Did you set WITH_APACHE and build and INDEX and use that ? - grep Makefile(s) - Use Default INDEX ? - Other ? -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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: [HEADS UP] Ports Infrastructure Changes
On Sat, Mar 19, 2011 at 12:53 PM, Philip M. Gollucci pgollu...@p6m7g8.comwrote: On 3/18/2011 9:49 PM, Martin Wilke wrote: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache How did you generate this list ? - Did you set WITH_APACHE and build and INDEX and use that ? - grep Makefile(s) - Use Default INDEX ? - Other ? reading port by port from scratch... -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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: [HEADS UP] Ports Infrastructure Changes
On 3/19/2011 12:51 AM, Philip M. Gollucci wrote: On 3/18/2011 9:49 PM, Martin Wilke wrote: Hey, as the Ports Collection continue to grow, we have decided to do some changes to the category layout. The www category, second largest with over 2000 individual ports, will have three subcategories spinned out. On the other side, x11-servers category, with only 10 ports, will be folded into regular x11 category. Attached is a proposed list of ports being moved from the www category. Please review, discuss and report ommissions and mistakes. The general key to the new categories is as follows: www-clients - browsers, rss clients, wget-alike, webapi/soap clients, benchmarks www-servers - http servers, proxy servers, everything related to apache What is the plan for updating all the *_DEPENDS line? esp libapreq, mod_perl ? -- 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. ___ 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
