ports/ languages categories
in [Ports]
|
From: David DEMELIER on 25 Jul 2010 06:26 Hello, I personally think that categories like french, japanese, arabic, etc... are not the best way to write a language dependant port. Now, there is no many languages categories in the ports tree but we can plan that in the future more directories for the new future languages dependant port can be added. Example : if someone write a new aspell language that is not in the ports tree, we must create a new directory in the ports tree ports/. For example: there is no ports/italian directory now, will you create a new italian directory if we must add aspell for italian? (no it's in textproc/it-aspell and it's confusing) I think we must remove all these languages directories and just keep it simple and simple like all the textproc/*-aspell. The best way to separate ports to language dependant port is just prefixing the port with the good language such as : fr-kde4-l10n fr-aspell de-ispell and so on. It's so easier to maintain and so much cleaner ! I hope you will agree with me. With kind regards. -- Demelier David _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Doug Barton on 25 Jul 2010 17:30 On Sun, 25 Jul 2010, David DEMELIER wrote: > Hello, > > I personally think that categories like french, japanese, arabic, > etc... are not the best way to write a language dependant port. Now, > there is no many languages categories in the ports tree but we can > plan that in the future more directories for the new future languages > dependant port can be added. Example : if someone write a new aspell > language that is not in the ports tree, we must create a new directory > in the ports tree ports/. > > For example: there is no ports/italian directory now, will you create > a new italian directory if we must add aspell for italian? (no it's in > textproc/it-aspell and it's confusing) For all of the literal categories (I.e., those that live in real directories) the path has always been that new things are introduced in whatever existing category is the most appropriate. Then at some point someone notices, "Hey, there are sure a lot of foo, maybe we should create ports/foo to put them all in." That suggestion goes to the -ports list, it gets discussed, if there is enough support for it then ports/foo is born and things are moved into it. Nothing about that procedure is different as it relates to the language-specific categories. hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
|
Pages: 1 Prev: net-im/libpurple forgot to remove patches? Next: tomcat 5.5 security fix |