Re: Where are conventions like -devel ports documented?

2012-03-27 Thread Alex Kozlov
On Sun, Mar 25, 2012 at 11:24:59PM +0300, Gerald Pfeifer wrote:
> Perhaps I am missing the obvious and will be rewarded with
> embarrassement, but where are conventions like the use and
> naming of -devel ports described?
> 
> I would have expected this to be covered in
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
> but -- it is not.
> 
> (If this is an omission, can someone more closely involved than
> I have been so far donate a paragraph or two?)
> 
> Gerald
> 
> PS: I am thinking to split the existing emulators/wine port into
> two, the regular one (tracking releases of Wine) and a -devel port
> that tracks the bi-weekly snapshots that will lead to the next
> release in a year or two.  Somehow I would prefer something like
> wine-stable / wine instead of wine / wine-devel, but the latter is
> more in line with how we are doing things, right?
In general, $port / $port-devel more common, but in case of wine I think
wine-stable or even wine14 / wine would be better. I suspect that not mouch
people would stick with wine release.


--
Adios
___
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: Where are conventions like -devel ports documented?

2012-03-25 Thread Wesley Shields
On Sun, Mar 25, 2012 at 11:24:59PM +0300, Gerald Pfeifer wrote:
> Perhaps I am missing the obvious and will be rewarded with
> embarrassement, but where are conventions like the use and
> naming of -devel ports described?
> 
> I would have expected this to be covered in
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
> but -- it is not.
> 
> (If this is an omission, can someone more closely involved than
> I have been so far donate a paragraph or two?)
> 
> Gerald
> 
> PS: I am thinking to split the existing emulators/wine port into
> two, the regular one (tracking releases of Wine) and a -devel port
> that tracks the bi-weekly snapshots that will lead to the next
> release in a year or two.  Somehow I would prefer something like
> wine-stable / wine instead of wine / wine-devel, but the latter is
> more in line with how we are doing things, right?

Correct, the latter is how things are done. I think of it this way: as a
user of wine I want the "wine" port/package to give me the best working
version while "wine-devel" to give me a development version, for
whatever "development version" means. It is clear to me that I'm getting
something not as well tested as the latest release.

-- WXS
___
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: Where are conventions like -devel ports documented?

2012-03-25 Thread Oliver Heesakkers
Op zo 25 mrt 2012 23:24:59 schreef Gerald Pfeifer:
> Perhaps I am missing the obvious and will be rewarded with
> embarrassement, but where are conventions like the use and
> naming of -devel ports described?
> 
> I would have expected this to be covered in
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
> but -- it is not.
> 

Try this section:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html#PORTING-PKGNAME
___
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"


Where are conventions like -devel ports documented?

2012-03-25 Thread Gerald Pfeifer
Perhaps I am missing the obvious and will be rewarded with
embarrassement, but where are conventions like the use and
naming of -devel ports described?

I would have expected this to be covered in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
but -- it is not.

(If this is an omission, can someone more closely involved than
I have been so far donate a paragraph or two?)

Gerald

PS: I am thinking to split the existing emulators/wine port into
two, the regular one (tracking releases of Wine) and a -devel port
that tracks the bi-weekly snapshots that will lead to the next
release in a year or two.  Somehow I would prefer something like
wine-stable / wine instead of wine / wine-devel, but the latter is
more in line with how we are doing things, right?
___
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"