Re: expiration of net/skype ?!
FYI, you're gonna see a nice update in the following days :) -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: expiration of net/skype ?!
On Sun, 1 May 2011 17:31:11 +0100 Chris Rees utis...@gmail.com wrote: On 1 May 2011 08:26, mato gam...@users.sf.net wrote: Chris Rees wrote: Mato wrote: Ok, from my understanding it wouldn't be the first time a port distfile is not (easily) available yet the port itself works if one can get the distfile. And it's very easy to search successfully the interwebs for this particular distfile. In such a case I see no reason to remove the port if it works (under condition one gets the distfile). I myself have it (and I even host it privately). And reading mailing lists reveals there are many people using the port. If one is capable of finding a distfile it's a trivial addition to find the port. Rather than having defective ports in the tree, perhaps you could host the Skype shar? With a decent title it'll probably show up early enough on a Google search. Chris That is one of possibilities. The question is whether we want to lower barriers for new / common users or not. Experience suggests that people will choose a different solution if it makes their life easier. See my other recent post please. Unfortunately, until the port is updated this will not be 'undeprecated'. It is not general policy to allow manual fetches unless a seriously major (ie Java) component requires it. Skype does not fit that mould; there are plenty of viable alternatives. There are other too (all of them annoying for me as a user), and there is not problem with this. But that is the upstream policy about distributing those distfiles -- we don't require users to google and find copies somewhere on the web. I'm not trying to brush you off; I'm just pointing out that the Project will not deliberately breach licensing conditions to make things We don't break them for any reason. easier for new users, neither is there a 'probably broken' part of the Ports tree -- the closest thing to a different repo is a separate tree, for example [1]. Chris [1] http://code.google.com/p/freebsd-texlive/ Anyway, work is underway to fully support newer skype versions, and the biggest part of the work in our linuxulator was done. Again, if you want skype, go on skype's forums and bug them about supporting FreeBSD or at least OSS suport. This being a binary product, there's very little we can realy do when somethign goes wrong. -- Ion-Mihai Tetcu ite...@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: expiration of net/skype ?!
Am 01.05.2011 09:18, schrieb Chris Rees: On 1 May 2011 07:58, mato gam...@users.sf.net wrote: Peter Jeremy wrote: On 2011-Apr-26 01:47:30 +0200, martinkogam...@users.sf.net wrote: So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. I believe work is underway to support the currently available version of Skype. Ok, from my understanding it wouldn't be the first time a port distfile is not (easily) available yet the port itself works if one can get the distfile. And it's very easy to search successfully the interwebs for this particular distfile. In such a case I see no reason to remove the port if it works (under condition one gets the distfile). I myself have it (and I even host it privately). And reading mailing lists reveals there are many people using the port. If one is capable of finding a distfile it's a trivial addition to find the port. Rather than having defective ports in the tree, perhaps you could host the Skype shar? With a decent title it'll probably show up early enough on a Google search. Nah, please let's keep the port in and have it issue download hints similar to the Java port (if legally possible) or otherwise issue a hint that the port is kept for the benefit of those who happen to have a distfile. ___ 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: expiration of net/skype ?!
On 1 May 2011 08:30, Matthias Andree mand...@freebsd.org wrote: Am 01.05.2011 09:18, schrieb Chris Rees: On 1 May 2011 07:58, mato gam...@users.sf.net wrote: Peter Jeremy wrote: On 2011-Apr-26 01:47:30 +0200, martinkogam...@users.sf.net wrote: So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. I believe work is underway to support the currently available version of Skype. Ok, from my understanding it wouldn't be the first time a port distfile is not (easily) available yet the port itself works if one can get the distfile. And it's very easy to search successfully the interwebs for this particular distfile. In such a case I see no reason to remove the port if it works (under condition one gets the distfile). I myself have it (and I even host it privately). And reading mailing lists reveals there are many people using the port. If one is capable of finding a distfile it's a trivial addition to find the port. Rather than having defective ports in the tree, perhaps you could host the Skype shar? With a decent title it'll probably show up early enough on a Google search. Nah, please let's keep the port in and have it issue download hints similar to the Java port (if legally possible) which it's not without being on dodgy ground or otherwise issue a hint that the port is kept for the benefit of those who happen to have a distfile. Which is what, thirty people? 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: expiration of net/skype ?!
Am 02.05.2011 10:49, schrieb Chris Rees: or otherwise issue a hint that the port is kept for the benefit of those who happen to have a distfile. Which is what, thirty people? I don't care. Let's not deliberately break the port for those who can still use it. Please remove the EXPIRATION_DATE; I'm also willing to maintain the port if needed. Best regards ___ 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: expiration of net/skype ?!
On Mon, 2 May 2011 12:14:37 +0100 Chris Rees utis...@gmail.com wrote: On 2 May 2011 10:03, Matthias Andree mand...@freebsd.org wrote: Am 02.05.2011 10:49, schrieb Chris Rees: or otherwise issue a hint that the port is kept for the benefit of those who happen to have a distfile. Which is what, thirty people? I don't care. Let's not deliberately break the port for those who can still use it. Please remove the EXPIRATION_DATE; I'm also willing to maintain the port if needed. Although the port is already broken (no-one is deliberately breaking it), there is a possible (temporary) solution for those who want to use their own distfile. ITetcu, miwi, please would you have a look at [1]? It's partly lifted from the diablo ports; just makes it more convenient if one has the distfile already, as well as using IGNORE rather than BROKEN; we know it won't ever build. Chris [1] http://www.bayofrum.net/~crees/patches/skype-distfile.diff Looks good; I was convinced something like this was already committed. -- Ion-Mihai Tetcu ite...@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: expiration of net/skype ?!
On 1 May 2011 07:58, mato gam...@users.sf.net wrote: Peter Jeremy wrote: On 2011-Apr-26 01:47:30 +0200, martinkogam...@users.sf.net wrote: So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. I believe work is underway to support the currently available version of Skype. Ok, from my understanding it wouldn't be the first time a port distfile is not (easily) available yet the port itself works if one can get the distfile. And it's very easy to search successfully the interwebs for this particular distfile. In such a case I see no reason to remove the port if it works (under condition one gets the distfile). I myself have it (and I even host it privately). And reading mailing lists reveals there are many people using the port. If one is capable of finding a distfile it's a trivial addition to find the port. Rather than having defective ports in the tree, perhaps you could host the Skype shar? With a decent title it'll probably show up early enough on a Google search. 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: expiration of net/skype ?!
Jason J. Hellenthal wrote: martinko, Hi, Ive read your post below and the following two messages on this among other messages regarding the deprecation of ports. One thing that should be noted is that once the deprecation process is done and over and the port nolonger becomes part of the tree, you are still more than able and welcome to keep the distfiles you have as well checkout just the port directory in question that you are worried about to a seperate place other than the ports tree to maintain it locally. The port may not exactly be in the snapshot tree but just because of that does not mean it will not work for you from a different location. Also note that it may actually be good practice for those that need to use those ports but are unsure of exactly what it involves to upkeep them. It could lead you to another time where you might be interested in being the maintainer for that port. On Tue, Apr 26, 2011 at 01:47:30AM +0200, martinko wrote: Hi all, So what is this deprecation and expiration of net/skype port please ?? I'm asking because I've been using it successfully for more than a year and installed it again just this weekend without any issue. And I've read in the mailing lists many others use it too. So why all that black-listing ? Should I copy the port to my home folder for future installations ? Or can I / we do something about keeping it in the ports tree ? I would surely appreciate if it could stay there. Hi Jason, Sure I can do it and it was part of my original question. The thing is that it's not only about myself -- whenever I would install FreeBSD (or PC-BSD) to someone and they would ask about Skype (which is very often) I would have to get the old port and distfile, which complicates things just a bit more. Also new users checking on what FreeBSD provides find that Skype is deprecated and that may be one more reason for them to avoid FreeBSD. I believe the project should make it easier, not more difficult, for people to get onboard. Even Linux distributions that want to keep their main repos clean of non-free software have problematic stuff in a non-free repo easily available. Regards, Martin ___ 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: expiration of net/skype ?!
Chris Rees wrote: On 1 May 2011 07:58, mato gam...@users.sf.net mailto:gam...@users.sf.net wrote: Peter Jeremy wrote: On 2011-Apr-26 01:47:30 +0200, martinkogam...@users.sf.net mailto:gam...@users.sf.net wrote: So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. I believe work is underway to support the currently available version of Skype. Ok, from my understanding it wouldn't be the first time a port distfile is not (easily) available yet the port itself works if one can get the distfile. And it's very easy to search successfully the interwebs for this particular distfile. In such a case I see no reason to remove the port if it works (under condition one gets the distfile). I myself have it (and I even host it privately). And reading mailing lists reveals there are many people using the port. If one is capable of finding a distfile it's a trivial addition to find the port. Rather than having defective ports in the tree, perhaps you could host the Skype shar? With a decent title it'll probably show up early enough on a Google search. Chris That is one of possibilities. The question is whether we want to lower barriers for new / common users or not. Experience suggests that people will choose a different solution if it makes their life easier. See my other recent post please. Regards, M. ___ 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: expiration of net/skype ?!
Peter Jeremy wrote: On 2011-Apr-26 01:47:30 +0200, martinkogam...@users.sf.net wrote: So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. I believe work is underway to support the currently available version of Skype. Ok, from my understanding it wouldn't be the first time a port distfile is not (easily) available yet the port itself works if one can get the distfile. And it's very easy to search successfully the interwebs for this particular distfile. In such a case I see no reason to remove the port if it works (under condition one gets the distfile). I myself have it (and I even host it privately). And reading mailing lists reveals there are many people using the port. In regards to new Skype version -- it's not available yet and from what I know it needs PulseAudio which may be a drawback for many. I personally would prefer this classic OSS version. So pls do not deprecate and surely do not remove the port! Thanks, Martin ___ 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: expiration of net/skype ?!
On 1 May 2011 08:26, mato gam...@users.sf.net wrote: Chris Rees wrote: Mato wrote: Ok, from my understanding it wouldn't be the first time a port distfile is not (easily) available yet the port itself works if one can get the distfile. And it's very easy to search successfully the interwebs for this particular distfile. In such a case I see no reason to remove the port if it works (under condition one gets the distfile). I myself have it (and I even host it privately). And reading mailing lists reveals there are many people using the port. If one is capable of finding a distfile it's a trivial addition to find the port. Rather than having defective ports in the tree, perhaps you could host the Skype shar? With a decent title it'll probably show up early enough on a Google search. Chris That is one of possibilities. The question is whether we want to lower barriers for new / common users or not. Experience suggests that people will choose a different solution if it makes their life easier. See my other recent post please. Unfortunately, until the port is updated this will not be 'undeprecated'. It is not general policy to allow manual fetches unless a seriously major (ie Java) component requires it. Skype does not fit that mould; there are plenty of viable alternatives. I'm not trying to brush you off; I'm just pointing out that the Project will not deliberately breach licensing conditions to make things easier for new users, neither is there a 'probably broken' part of the Ports tree -- the closest thing to a different repo is a separate tree, for example [1]. Chris [1] http://code.google.com/p/freebsd-texlive/ ___ 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: expiration of net/skype ?!
On Tue, 26 Apr 2011 10:29:16 +1000 Peter Jeremy peterjer...@acm.org wrote: On 2011-Apr-26 01:47:30 +0200, martinko gam...@users.sf.net wrote: So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. True, and we've kept it like this for a long time. I have asked people at skype to allow us to redistribute the distfile, but that's impossible for legal reasons (not theirs). I believe work is underway to support the currently available version of Skype. It is, and it's kinda workoing on HEAD plus some patches. One thing all of oyu could do is bug skype on their forums to provide an OSS version; I recently argued about that with their linux product manager, so more voices would help. -- Ion-Mihai Tetcu ite...@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: expiration of net/skype ?!
martinko, Hi, Ive read your post below and the following two messages on this among other messages regarding the deprecation of ports. One thing that should be noted is that once the deprecation process is done and over and the port nolonger becomes part of the tree, you are still more than able and welcome to keep the distfiles you have as well checkout just the port directory in question that you are worried about to a seperate place other than the ports tree to maintain it locally. The port may not exactly be in the snapshot tree but just because of that does not mean it will not work for you from a different location. Also note that it may actually be good practice for those that need to use those ports but are unsure of exactly what it involves to upkeep them. It could lead you to another time where you might be interested in being the maintainer for that port. On Tue, Apr 26, 2011 at 01:47:30AM +0200, martinko wrote: Hi all, So what is this deprecation and expiration of net/skype port please ?? I'm asking because I've been using it successfully for more than a year and installed it again just this weekend without any issue. And I've read in the mailing lists many others use it too. So why all that black-listing ? Should I copy the port to my home folder for future installations ? Or can I / we do something about keeping it in the ports tree ? I would surely appreciate if it could stay there. -- Regards, (jhell) Jason Hellenthal pgpEgF7qh4JeD.pgp Description: PGP signature
expiration of net/skype ?!
Hi all, So what is this deprecation and expiration of net/skype port please ?? I'm asking because I've been using it successfully for more than a year and installed it again just this weekend without any issue. And I've read in the mailing lists many others use it too. So why all that black-listing ? Should I copy the port to my home folder for future installations ? Or can I / we do something about keeping it in the ports tree ? I would surely appreciate if it could stay there. With regards, Martin ___ 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: expiration of net/skype ?!
On 2011-Apr-26 01:47:30 +0200, martinko gam...@users.sf.net wrote: So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. I believe work is underway to support the currently available version of Skype. -- Peter Jeremy pgpy5lTilUuxC.pgp Description: PGP signature
