Re: FreeBSD Port: xpra-0.0.7.16p4
To the extent I understand all this, it sounds reasonable, albeit complex. You might want to consider setting up a new project on sourceforge, google code, etc. but I'll leave that up to you and swills. Thanks for answering my questions. Doug On 02/04/2011 13:59, Antoine Martin wrote: Hi Doug, The last proper file release from upstream was 0.0.6 in November 2009. Since then, I've fixed a number of things (from typos to build fixes for some platforms), supported new platforms (mac osx, I originally added win32 support but the author then re-wrote that), etc Any help in getting the patches merged would be much appreciated, I haven't had much luck so far. I used to send piecemeal patches with full description to the author, but since almost none of them got merged, recently I've started posting large all-in-one diffs instead. (they're not even all from me these patches, but I end up maintaining them) Also, another tool I maintain won't work without the patches I added, so if you ship the upstream version then I'll have to fork it to make it work with my tool (I really really would rather not). Cheers Antoine On 02/05/2011 02:56 AM, Doug Barton wrote: I'm confused. Why are we not using the sources from the "regular" location, and patching to make them work for us? And has anyone contacted the upstream about the changes and why they are necessary? This whole thing seems very confusing to me (but that's not saying much). :) Doug ___ 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: FreeBSD Port: xpra-0.0.7.16p4
Hi Doug, The last proper file release from upstream was 0.0.6 in November 2009. Since then, I've fixed a number of things (from typos to build fixes for some platforms), supported new platforms (mac osx, I originally added win32 support but the author then re-wrote that), etc Any help in getting the patches merged would be much appreciated, I haven't had much luck so far. I used to send piecemeal patches with full description to the author, but since almost none of them got merged, recently I've started posting large all-in-one diffs instead. (they're not even all from me these patches, but I end up maintaining them) Also, another tool I maintain won't work without the patches I added, so if you ship the upstream version then I'll have to fork it to make it work with my tool (I really really would rather not). Cheers Antoine On 02/05/2011 02:56 AM, Doug Barton wrote: > I'm confused. Why are we not using the sources from the "regular" > location, and patching to make them work for us? And has anyone > contacted the upstream about the changes and why they are necessary? > This whole thing seems very confusing to me (but that's not saying > much). :) > > Doug > > > ___ 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: FreeBSD Port: xpra-0.0.7.16p4
I'm confused. Why are we not using the sources from the "regular" location, and patching to make them work for us? And has anyone contacted the upstream about the changes and why they are necessary? This whole thing seems very confusing to me (but that's not saying much). :) 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: FreeBSD Port: xpra-0.0.7.16p4
On Fri, Feb 04, 2011 at 09:49:39AM +0100, Kurt Jaeger wrote: > Hi! > > > >> I only just noticed that you've added a port for xpra. > > >> I wasn't aware of that and you're pointing to the source on my server, > > >> so I guess that it means I have to be careful not to remove it from now > > >> on? > > > > > > The files should eventually get automatically mirrored to the FreeBSD > > > ftp server at ftp.freebsd.org (and it's mirrors), so worst case users > > > get it from there, but it's always nice to get it from the originator. > > > OK, I normally move old source releases to /old/ eventually. > > I guess I can still do that as long as the port file has been updated to > > use the newer source snapshots? > > There are always hosts out there that still have old port Makefiles > on their disks, so having a stable path would be useful. > > E.g. on cpan, the files just are added to the directory, not moved > after newer ones are added. Well, in truth, the port's Makefile may be trivially configured to look into the old/ subdirectory if the distfile is not found in the "real" one (see the security/stunnel Makefile for an example). G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@freebsd.org pe...@packetscale.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This inert sentence is my body, but my soul is alive, dancing in the sparks of your brain. signature.asc Description: Digital signature
Re: FreeBSD Port: xpra-0.0.7.16p4
Hi! > > There are always hosts out there that still have old port Makefiles > > on their disks, so having a stable path would be useful. > Well, in truth, the port's Makefile may be trivially configured to look > into the old/ subdirectory if the distfile is not found in the "real" one > (see the security/stunnel Makefile for an example). Ah, I was not aware of that. Which part of the config provides this ? The /%SUBDIR%/ in combination with the MASTER_SITE_SUBDIR ? -- p...@opsec.eu+49 171 3101372 9 years to go ! ___ 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: FreeBSD Port: xpra-0.0.7.16p4
Hi! > >> I only just noticed that you've added a port for xpra. > >> I wasn't aware of that and you're pointing to the source on my server, > >> so I guess that it means I have to be careful not to remove it from now on? > > > > The files should eventually get automatically mirrored to the FreeBSD > > ftp server at ftp.freebsd.org (and it's mirrors), so worst case users > > get it from there, but it's always nice to get it from the originator. > OK, I normally move old source releases to /old/ eventually. > I guess I can still do that as long as the port file has been updated to > use the newer source snapshots? There are always hosts out there that still have old port Makefiles on their disks, so having a stable path would be useful. E.g. on cpan, the files just are added to the directory, not moved after newer ones are added. -- p...@opsec.eu+49 171 3101372 9 years to go ! ___ 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: FreeBSD Port: xpra-0.0.7.16p4
On 02/04/2011 06:53 AM, Steve Wills wrote: > On 02/03/11 15:15, Antoine Martin wrote: >> Hi there, > >> I only just noticed that you've added a port for xpra. >> I wasn't aware of that and you're pointing to the source on my server, >> so I guess that it means I have to be careful not to remove it from now on? > > The files should eventually get automatically mirrored to the FreeBSD > ftp server at ftp.freebsd.org (and it's mirrors), so worst case users > get it from there, but it's always nice to get it from the originator. > OK, I normally move old source releases to /old/ eventually. I guess I can still do that as long as the port file has been updated to use the newer source snapshots? Is it ok to remove source for out-of-date port files like that? Or is this frowned upon? Is there a policy at all? >> In the future, a simple notification email could prevent me from >> breaking stuff unintentionally. > > Noted. I only used that source because it compiled properly (due to your > changes), which the source hosted at Google Code didn't. I can mirror a > copy on my server and point users to that if you like. Upstream seems very slow at merging fixes and enhancements, not sure why. I don't have any problems with ports pointing to my server. :) >> FYI: the current version in: >> http://winswitch.org/src/ >> is 0.0.7.17-1 and it fixes a number of bugs, you should probably bump >> the port to this version. > > I'll work on that, thanks for the heads up. I hadn't seen a notice to > the parti-discuss list, which is where I saw your source originally. Hah, ok. Since upstream doesn't merge fixes very often, I don't always post updated patches there. I'll make sure to ping you from now on if you like. This normally coincides with a winswitch release, that I post here: http://lists.devloop.org.uk/mailman/listinfo/shifter-users >> One question: what would I have to do to get winswitch also into ports? >> It's trivial to install compared to xpra (as it's pure python), but it >> would still be nicer for users to get it all directly from ports. > > It would just take someone writing a port for it and submitting it. I > will work on that, but if you beat me to it I won't be offended. Great, keep me posted, I may yet find the time to look into it. (it's been on my todo list for over a year now..) Thanks! Antoine > > Thanks for the info! > > Steve ___ 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: FreeBSD Port: xpra-0.0.7.16p4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/11 15:15, Antoine Martin wrote: > Hi there, > > I only just noticed that you've added a port for xpra. > I wasn't aware of that and you're pointing to the source on my server, > so I guess that it means I have to be careful not to remove it from now on? The files should eventually get automatically mirrored to the FreeBSD ftp server at ftp.freebsd.org (and it's mirrors), so worst case users get it from there, but it's always nice to get it from the originator. > In the future, a simple notification email could prevent me from > breaking stuff unintentionally. Noted. I only used that source because it compiled properly (due to your changes), which the source hosted at Google Code didn't. I can mirror a copy on my server and point users to that if you like. > FYI: the current version in: > http://winswitch.org/src/ > is 0.0.7.17-1 and it fixes a number of bugs, you should probably bump > the port to this version. I'll work on that, thanks for the heads up. I hadn't seen a notice to the parti-discuss list, which is where I saw your source originally. > One question: what would I have to do to get winswitch also into ports? > It's trivial to install compared to xpra (as it's pure python), but it > would still be nicer for users to get it all directly from ports. It would just take someone writing a port for it and submitting it. I will work on that, but if you beat me to it I won't be offended. Thanks for the info! Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBAgAGBQJNS0AKAAoJEPXPYrMgexuhtKoIAKk/JP3dsbzCRYVWwXlrtTgg I3cG69CLUirTyczl2cc339hK/jPGrGbyvqjb0CMirGH5YJb8Nd/7of4h6GK6pRCl HVeZXAXEmTCVvuIozxR2U8aSBJ/XG+RgMmLD5ZF25Pa7RW0LsQfrfQ/Yc2YFs5hC 7qW92B+KXvH5M6nPqcG/FPcD6E7QyIsumOf+BUVo27C/0crBYWWGo/9R/IjzeRnW wCv6p3QdYM/xRr1BrBemr05/sB221rDY6u33yu7NQNST8cww5rluTaWxnmPhVzxb SYxbvA+VnIsx7NKD90ajeyj+YFh+gfUNXu65oiCM0Ai/EmQgBEaPRPqKZhS54eU= =g8I6 -END PGP SIGNATURE- ___ 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 Port: xpra-0.0.7.16p4
Hi there, I only just noticed that you've added a port for xpra. I wasn't aware of that and you're pointing to the source on my server, so I guess that it means I have to be careful not to remove it from now on? In the future, a simple notification email could prevent me from breaking stuff unintentionally. FYI: the current version in: http://winswitch.org/src/ is 0.0.7.17-1 and it fixes a number of bugs, you should probably bump the port to this version. One question: what would I have to do to get winswitch also into ports? It's trivial to install compared to xpra (as it's pure python), but it would still be nicer for users to get it all directly from ports. Cheers Antoine ___ 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"
