Re: xorg-server 1.7.7
Hi, Slowly i get my time back to work on FreeBSD, i'll start working next week on a xorg update. if someone want to help, please ping me via privat mail or irc. - Miwi On Tue, Nov 16, 2010 at 3:00 AM, Doug Barton do...@freebsd.org wrote: On 11/15/2010 02:51, Tijl Coosemans wrote: It would be better if there was a repo for ports development on the FreeBSD servers. There are several projects now that could use this that I think this is warranted. It would increase their visibility and lower the barrier to entry to attract contributors and testers. This would be quite easily accomplished by branching the ports tree we have no in CVS. Doing this would accomplish a lot of goals: 1. Make it easier for users to pick up and test new ports 2. Make it easier for the experimental trees to keep up to date with the canonical ports tree 3. Allow us to have a stable ports tree that users can check out and be reasonably well assured that everything in it will work together safely. 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 ___ 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: xorg-server 1.7.7
on 14/11/2010 21:06 Peter Jeremy said the following: On 2010-Nov-13 21:35:29 +0200, Andriy Gapon a...@icyb.net.ua wrote: I think that you refer to upgrades of the Xorg bundle as a whole. Not sure if we've had any problems like that when upgrading between minor versions of a single module, even such as xorg server. Looking back through my gripe list, apart from the general X11 build system regressions going from 6.9 to 7.0 (reducing portability and roughly doubling the overall build time), _all_ of the regressions, POLA violations and general breakage I have run into have been related to the X server (though some may be DRI/DRM and input/output device). Actually, now even I can recall my confusion with (1) change of default background in root window from the pattern to black; (2) adding dependency on hald and all that came along by default. But I believe that things like that do not happen between minor releases. Anyway, more incentive for all to do testing in advance. -- Andriy Gapon ___ 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: xorg-server 1.7.7
On Sunday 14 November 2010 23:02:42 Josh Paetzel wrote: Area51 is quite cloneable it terms of infrastructure and what not. We could very easily provide an SVN repo for experimental xoeg work. It would be better if there was a repo for ports development on the FreeBSD servers. There are several projects now that could use this that I think this is warranted. It would increase their visibility and lower the barrier to entry to attract contributors and testers. It doesn't have to be anything complicated. An SVN repo that tracks CVS and on which ports committers can create project branches would be enough. signature.asc Description: This is a digitally signed message part.
Re: xorg-server 1.7.7
On Sun, 14 Nov 2010 12:24:44 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Sun, 14 Nov 2010, Andriy Gapon wrote: on 14/11/2010 18:18 Warren Block said the following: On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Would it be really worth it? 1.7.7 is just couple of minor releases ahead of what we have now and the latest _release_ is 1.9.2. So, xorg-server-devel for 1.9.2 - that would make sense for my taste. xorg-server-devel for 1.7.7 - just an overcautiousness and, IMO, a waste of resources. It would depend on how compatible the newer server is with the existing xorg ports. But sure, go with the newest one that still works. 1.9.2 requires an update of MESA to a much more recent version than we currently have in ports. I tried the modify Makefile and install route yesterday and it failed because of that. If these ports are too shaky for normal users, they wouldn't even have to go in the tree. Put them on a web page somewhere. But this would ast least allow a wider range of testing. I installed 1.7.7 the end of September, without modifying/reinstalling any other ports, and it just worked. -- Gary Jennejohn ___ 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: xorg-server 1.7.7
On Monday, November 15, 2010 04:51:36 am Tijl Coosemans wrote: On Sunday 14 November 2010 23:02:42 Josh Paetzel wrote: Area51 is quite cloneable it terms of infrastructure and what not. We could very easily provide an SVN repo for experimental xoeg work. It would be better if there was a repo for ports development on the FreeBSD servers. There are several projects now that could use this that I think this is warranted. It would increase their visibility and lower the barrier to entry to attract contributors and testers. It doesn't have to be anything complicated. An SVN repo that tracks CVS and on which ports committers can create project branches would be enough. While conceptually that sounds very simple, an SVN repo that tracks a CVS repo is very complicated. One of the most complicated parts of the FreeBSD src repo being in SVN is the SVN - CVS exporter. The main issue is there are operations that don't map 1:1 across both repos that have to be dealt with by hand. I wasn't proposing that, I think area51 is just a place to check in experimental ports. The merge back to FreeBSD has to be done by hand. The main difference to me is by running it on a PC-BSD infrastructure box I can just set it up today and have it running and usable in a few hours. Punting it back to the FreeBSD projectby the time it's all sorted and up and running it will be spring of 2011. :) -- Thanks, Josh Paetzel Director of IT, iXsystems Servers For Open Source http://www.ixsystems.com signature.asc Description: This is a digitally signed message part.
Re: xorg-server 1.7.7
on 15/11/2010 16:16 Gary Jennejohn said the following: 1.9.2 requires an update of MESA to a much more recent version than we currently have in ports. I tried the modify Makefile and install route yesterday and it failed because of that. I have installed and been using newer Mesa for quite a while now, without any issue. I also satisfied other updates needed for xorg server 1.9.2 (don't remember what they were, some two other xorg lightweight ports). But personally for me the following bug is a showstopper for using 1.8.x or 1.9.x: https://bugs.freedesktop.org/show_bug.cgi?id=28181 I installed 1.7.7 the end of September, without modifying/reinstalling any other ports, and it just worked. This matches my experience too - no hassle, no problems. -- Andriy Gapon ___ 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: xorg-server 1.7.7
On 14.11.2010 22:00, Kris Moore wrote: On Sun 14/11/10 3:44 PM , Anonymous swel...@gmail.com wrote: Kris Moore writes: On Sun, Nov 14, 2010 at 12:24:44PM -0700, Warren Block wrote: On Sun, 14 Nov 2010, Andriy Gapon wrote: on 14/11/2010 18:18 Warren Block said the following: On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Would it be really worth it? 1.7.7 is just couple of minor releases ahead of what we have now and the latest _release_ is 1.9.2. So, xorg-server-devel for 1.9.2 - that would make sense for my taste. xorg-server-devel for 1.7.7 - just an overcautiousness and, IMO, a waste of resources. It would depend on how compatible the newer server is with the existing xorg ports. But sure, go with the newest one that still works. If these ports are too shaky for normal users, they wouldn't even have to go in the tree. Put them on a web page somewhere. But this would ast least allow a wider range of testing. Does the xorg porting team have a repo somewhere for port work, ala area51 for KDE4? If not, would setting one up be of interest to people here? That probably be a service we could easily provide, since we are particularly attached to having a working Xorg ;) It has one http://wiki.freebsd.org/ModularXorg/7.5 Not sure about previous major updates. With history scattered across several development repos[*] it can be quite hard to track. [*] no one uses branches in ports tree (shuns CVS?) Are those SVN services still in use? Looking at the http links on that page I assumed it was old and no longer usable. The server and the repository is still available but nobody is using it at the moment. So I forgot to update the configuration for the xorg-dev repo with the last server update. This should be fixed now. Beat ___ 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: xorg-server 1.7.7
On 11/15/2010 02:51, Tijl Coosemans wrote: It would be better if there was a repo for ports development on the FreeBSD servers. There are several projects now that could use this that I think this is warranted. It would increase their visibility and lower the barrier to entry to attract contributors and testers. This would be quite easily accomplished by branching the ports tree we have no in CVS. Doing this would accomplish a lot of goals: 1. Make it easier for users to pick up and test new ports 2. Make it easier for the experimental trees to keep up to date with the canonical ports tree 3. Allow us to have a stable ports tree that users can check out and be reasonably well assured that everything in it will work together safely. 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: xorg-server 1.7.7
On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Assuming no other dependencies, or at least a clear list of what to rebuild in the pkg-message, it would allow people to test the new xorg-server and easily revert to the old one if needed. Mesa, too... and what was the other port talked about recently... libdrm? ___ 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: xorg-server 1.7.7
on 14/11/2010 18:18 Warren Block said the following: On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Would it be really worth it? 1.7.7 is just couple of minor releases ahead of what we have now and the latest _release_ is 1.9.2. So, xorg-server-devel for 1.9.2 - that would make sense for my taste. xorg-server-devel for 1.7.7 - just an overcautiousness and, IMO, a waste of resources. Assuming no other dependencies, or at least a clear list of what to rebuild in the pkg-message, it would allow people to test the new xorg-server and easily revert to the old one if needed. Mesa, too... and what was the other port talked about recently... libdrm? -- Andriy Gapon ___ 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: xorg-server 1.7.7
On Sat, Nov 13, 2010 at 09:35:29PM +0200, Andriy Gapon wrote: Not sure if we've had any problems like that when upgrading between minor versions of a single module, even such as xorg server. I don't remember, either. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). rnoland was doing testing with some of the well-known configurations, to make sure those didn't regress. I'd be happy to see various folks step forward to volunteer to beta-test new updates on various configurations. Obviously, 100% coverage is impossible, but if we had a handful of folks, I think we could do a lot. 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: xorg-server 1.7.7
On Mon, 08 Nov 2010 11:22:37 +0200 Andriy Gapon a...@icyb.net.ua wrote: Can we update xorg-server to 1.7.7, the latest version on 1.7 branch? It looks like that would require only changing the version and regenerating the checksums. -- Andriy Gapon I'm going to update x11/pixman to 0.18.4 next week. Because the cairo 0.10 that comes with gnome 2.32 needs it. I haven't seen or heard from our testers that there where any problems with this update. -Koop ___ 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: xorg-server 1.7.7
On Sun, 14 Nov 2010, Andriy Gapon wrote: on 14/11/2010 18:18 Warren Block said the following: On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Would it be really worth it? 1.7.7 is just couple of minor releases ahead of what we have now and the latest _release_ is 1.9.2. So, xorg-server-devel for 1.9.2 - that would make sense for my taste. xorg-server-devel for 1.7.7 - just an overcautiousness and, IMO, a waste of resources. It would depend on how compatible the newer server is with the existing xorg ports. But sure, go with the newest one that still works. If these ports are too shaky for normal users, they wouldn't even have to go in the tree. Put them on a web page somewhere. But this would ast least allow a wider range of testing. ___ 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: xorg-server 1.7.7
On Sun, Nov 14, 2010 at 12:24:44PM -0700, Warren Block wrote: On Sun, 14 Nov 2010, Andriy Gapon wrote: on 14/11/2010 18:18 Warren Block said the following: On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Would it be really worth it? 1.7.7 is just couple of minor releases ahead of what we have now and the latest _release_ is 1.9.2. So, xorg-server-devel for 1.9.2 - that would make sense for my taste. xorg-server-devel for 1.7.7 - just an overcautiousness and, IMO, a waste of resources. It would depend on how compatible the newer server is with the existing xorg ports. But sure, go with the newest one that still works. If these ports are too shaky for normal users, they wouldn't even have to go in the tree. Put them on a web page somewhere. But this would ast least allow a wider range of testing. Does the xorg porting team have a repo somewhere for port work, ala area51 for KDE4? If not, would setting one up be of interest to people here? That probably be a service we could easily provide, since we are particularly attached to having a working Xorg ;) -- Kris Moore PC-BSD Software ___ 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: xorg-server 1.7.7
Kris Moore k...@pcbsd.org writes: On Sun, Nov 14, 2010 at 12:24:44PM -0700, Warren Block wrote: On Sun, 14 Nov 2010, Andriy Gapon wrote: on 14/11/2010 18:18 Warren Block said the following: On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Would it be really worth it? 1.7.7 is just couple of minor releases ahead of what we have now and the latest _release_ is 1.9.2. So, xorg-server-devel for 1.9.2 - that would make sense for my taste. xorg-server-devel for 1.7.7 - just an overcautiousness and, IMO, a waste of resources. It would depend on how compatible the newer server is with the existing xorg ports. But sure, go with the newest one that still works. If these ports are too shaky for normal users, they wouldn't even have to go in the tree. Put them on a web page somewhere. But this would ast least allow a wider range of testing. Does the xorg porting team have a repo somewhere for port work, ala area51 for KDE4? If not, would setting one up be of interest to people here? That probably be a service we could easily provide, since we are particularly attached to having a working Xorg ;) It has one http://wiki.freebsd.org/ModularXorg/7.5 Not sure about previous major updates. With history scattered across several development repos[*] it can be quite hard to track. [*] no one uses branches in ports tree (shuns CVS?) ___ 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: xorg-server 1.7.7
On 2010-Nov-13 21:35:29 +0200, Andriy Gapon a...@icyb.net.ua wrote: I think that you refer to upgrades of the Xorg bundle as a whole. Not sure if we've had any problems like that when upgrading between minor versions of a single module, even such as xorg server. Looking back through my gripe list, apart from the general X11 build system regressions going from 6.9 to 7.0 (reducing portability and roughly doubling the overall build time), _all_ of the regressions, POLA violations and general breakage I have run into have been related to the X server (though some may be DRI/DRM and input/output device). -- Peter Jeremy pgp8u8GKT30Fb.pgp Description: PGP signature
Re: xorg-server 1.7.7
On Sun 14/11/10 3:44 PM , Anonymous swel...@gmail.com wrote: Kris Moore writes: On Sun, Nov 14, 2010 at 12:24:44PM -0700, Warren Block wrote: On Sun, 14 Nov 2010, Andriy Gapon wrote: on 14/11/2010 18:18 Warren Block said the following: On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Would it be really worth it? 1.7.7 is just couple of minor releases ahead of what we have now and the latest _release_ is 1.9.2. So, xorg-server-devel for 1.9.2 - that would make sense for my taste. xorg-server-devel for 1.7.7 - just an overcautiousness and, IMO, a waste of resources. It would depend on how compatible the newer server is with the existing xorg ports. But sure, go with the newest one that still works. If these ports are too shaky for normal users, they wouldn't even have to go in the tree. Put them on a web page somewhere. But this would ast least allow a wider range of testing. Does the xorg porting team have a repo somewhere for port work, ala area51 for KDE4? If not, would setting one up be of interest to people here? That probably be a service we could easily provide, since we are particularly attached to having a working Xorg ;) It has one http://wiki.freebsd.org/ModularXorg/7.5 Not sure about previous major updates. With history scattered across several development repos[*] it can be quite hard to track. [*] no one uses branches in ports tree (shuns CVS?) Are those SVN services still in use? Looking at the http links on that page I assumed it was old and no longer usable. -- Kris Moore PC-BSD / iXsystems Message sent via Atmail Open - http://atmail.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: xorg-server 1.7.7
Area51 is quite cloneable it terms of infrastructure and what not. We could very easily provide an SVN repo for experimental xoeg work. Thanks, Josh Paetzel On Nov 14, 2010, at 3:00 PM, Kris Moore k...@pcbsd.org wrote: On Sun 14/11/10 3:44 PM , Anonymous swel...@gmail.com wrote: Kris Moore writes: On Sun, Nov 14, 2010 at 12:24:44PM -0700, Warren Block wrote: On Sun, 14 Nov 2010, Andriy Gapon wrote: on 14/11/2010 18:18 Warren Block said the following: On Sat, 13 Nov 2010, Andriy Gapon wrote: I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). Why not just create a new xorg-server177 or xorg-server-devel port as has been done with other ports? Would it be really worth it? 1.7.7 is just couple of minor releases ahead of what we have now and the latest _release_ is 1.9.2. So, xorg-server-devel for 1.9.2 - that would make sense for my taste. xorg-server-devel for 1.7.7 - just an overcautiousness and, IMO, a waste of resources. It would depend on how compatible the newer server is with the existing xorg ports. But sure, go with the newest one that still works. If these ports are too shaky for normal users, they wouldn't even have to go in the tree. Put them on a web page somewhere. But this would ast least allow a wider range of testing. Does the xorg porting team have a repo somewhere for port work, ala area51 for KDE4? If not, would setting one up be of interest to people here? That probably be a service we could easily provide, since we are particularly attached to having a working Xorg ;) It has one http://wiki.freebsd.org/ModularXorg/7.5 Not sure about previous major updates. With history scattered across several development repos[*] it can be quite hard to track. [*] no one uses branches in ports tree (shuns CVS?) Are those SVN services still in use? Looking at the http links on that page I assumed it was old and no longer usable. -- Kris Moore PC-BSD / iXsystems Message sent via Atmail Open - http://atmail.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: xorg-server 1.7.7
On Mon, Nov 08, 2010 at 05:11:41PM +0200, Andriy Gapon wrote: Oh, forgot a need to simply bump port revisions of all xorg driver ports. That's perhaps a little bit laborious, but doesn't require any special skills. Or did you have something else in mind? There's this whole testing thing :-) xorg seems to have an amazing ability to introduce regressions, especially in edge cases/older hardware. Each of the last N updates has been preceded by a lot of staging/testing, and even so, created a lot of work to clean everything up. So, in theory, it's easy, but in practice, it requires someone(s) with a lot of time and dedication. We certainly need one or more such people right now! 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: xorg-server 1.7.7
on 13/11/2010 21:25 Mark Linimon said the following: There's this whole testing thing :-) So, I thought taht I contributed one test report already :-) xorg seems to have an amazing ability to introduce regressions, especially in edge cases/older hardware. Each of the last N updates has been preceded by a lot of staging/testing, and even so, created a lot of work to clean everything up. I think that you refer to upgrades of the Xorg bundle as a whole. Not sure if we've had any problems like that when upgrading between minor versions of a single module, even such as xorg server. So, in theory, it's easy, but in practice, it requires someone(s) with a lot of time and dedication. We certainly need one or more such people right now! I agree, but I am not sure how in the ports land we do an application testing in general. That is, I am sure there will be a lot of testers if the port update is actually committed :-) but I am not sure how to test it in advance (given all the possible hardware and software configurations). -- Andriy Gapon ___ 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
xorg-server 1.7.7
Can we update xorg-server to 1.7.7, the latest version on 1.7 branch? It looks like that would require only changing the version and regenerating the checksums. -- Andriy Gapon ___ 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: xorg-server 1.7.7
On Mon, Nov 08, 2010 at 11:22:37AM +0200, Andriy Gapon wrote: Can we update xorg-server to 1.7.7, the latest version on 1.7 branch? It looks like that would require only changing the version and regenerating the checksums. Seems to be not so trivial. Look at this thread: http://lists.freebsd.org/pipermail/freebsd-ports/2010-May/061141.html Since miwi@ and rnoland@ seem to be busy at moment there is a need for the maintainer of ALL of the xorg-* ports (and not only the single ones, like xorg-server, etc.). Someone with enough time, motivation (hardware, programming foo in this area...) Just 0.02$, :-( Alexey. ___ 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: xorg-server 1.7.7
on 08/11/2010 17:03 Alexey Shuvaev said the following: On Mon, Nov 08, 2010 at 11:22:37AM +0200, Andriy Gapon wrote: Can we update xorg-server to 1.7.7, the latest version on 1.7 branch? It looks like that would require only changing the version and regenerating the checksums. Seems to be not so trivial. Look at this thread: http://lists.freebsd.org/pipermail/freebsd-ports/2010-May/061141.html Since miwi@ and rnoland@ seem to be busy at moment there is a need for the maintainer of ALL of the xorg-* ports (and not only the single ones, like xorg-server, etc.). Someone with enough time, motivation (hardware, programming foo in this area...) Oh, forgot a need to simply bump port revisions of all xorg driver ports. That's perhaps a little bit laborious, but doesn't require any special skills. Or did you have something else in mind? -- Andriy Gapon ___ 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: xorg-server 1.7.7
On Mon, Nov 08, 2010 at 05:11:41PM +0200, Andriy Gapon wrote: on 08/11/2010 17:03 Alexey Shuvaev said the following: On Mon, Nov 08, 2010 at 11:22:37AM +0200, Andriy Gapon wrote: Can we update xorg-server to 1.7.7, the latest version on 1.7 branch? It looks like that would require only changing the version and regenerating the checksums. Seems to be not so trivial. Look at this thread: http://lists.freebsd.org/pipermail/freebsd-ports/2010-May/061141.html Since miwi@ and rnoland@ seem to be busy at moment there is a need for the maintainer of ALL of the xorg-* ports (and not only the single ones, like xorg-server, etc.). Someone with enough time, motivation (hardware, programming foo in this area...) Oh, forgot a need to simply bump port revisions of all xorg driver ports. That's perhaps a little bit laborious, but doesn't require any special skills. Or did you have something else in mind? Well, I'm successfully running xorg-server-1.7.7 since May without doing anything else to other xorg-related ports: xorg-server-1.7.7,1succeeds index (index has 1.7.5,1) but it could be just a matter of luck :) I mean this (from rnolad): I have an update to 1.7.7 queued up in my tree along with an updated pixman. It is a little tedious as all of the server based ports need to be updated and drivers need PORTREVISION bumps. I'll try and get it committed in the next couple of days though. He mentions update (not just PORTREVISION bump) of pixman and other server-based ports. I have some vague insight into what he means, but I'd say it should be done by a person more familiar (than me) with xorg infrastucture with all its interdependencies. Alexey. ___ 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: xorg-server 1.7.7
on 08/11/2010 17:52 Alexey Shuvaev said the following: On Mon, Nov 08, 2010 at 05:11:41PM +0200, Andriy Gapon wrote: on 08/11/2010 17:03 Alexey Shuvaev said the following: On Mon, Nov 08, 2010 at 11:22:37AM +0200, Andriy Gapon wrote: Can we update xorg-server to 1.7.7, the latest version on 1.7 branch? It looks like that would require only changing the version and regenerating the checksums. Seems to be not so trivial. Look at this thread: http://lists.freebsd.org/pipermail/freebsd-ports/2010-May/061141.html Since miwi@ and rnoland@ seem to be busy at moment there is a need for the maintainer of ALL of the xorg-* ports (and not only the single ones, like xorg-server, etc.). Someone with enough time, motivation (hardware, programming foo in this area...) Oh, forgot a need to simply bump port revisions of all xorg driver ports. That's perhaps a little bit laborious, but doesn't require any special skills. Or did you have something else in mind? Well, I'm successfully running xorg-server-1.7.7 since May without doing anything else to other xorg-related ports: xorg-server-1.7.7,1succeeds index (index has 1.7.5,1) but it could be just a matter of luck :) Me too :-) But I think that I did have to rebuild xorg drivers that I use because they refused to load after xorg-server upgrade. But perhaps I misremember my experiment with 1.8.2 or 1.9.2. I mean this (from rnolad): I have an update to 1.7.7 queued up in my tree along with an updated pixman. It is a little tedious as all of the server based ports need to be updated and drivers need PORTREVISION bumps. I'll try and get it committed in the next couple of days though. He mentions update (not just PORTREVISION bump) of pixman and other server-based ports. I have some vague insight into what he means, but I'd say it should be done by a person more familiar (than me) with xorg infrastucture with all its interdependencies. Well, I think that those were meant as bonuses, not as requirements. -- Andriy Gapon ___ 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: xorg-server 1.7.7
Hi, Oh, forgot a need to simply bump port revisions of all xorg driver ports. That's perhaps a little bit laborious, but doesn't require any special skills. Or did you have something else in mind? more than just laborious. It will break at least the Intel driver as intel is now GEM only which is not available on FreeBSD yet. Christof -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments ___ 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: xorg-server 1.7.7
on 08/11/2010 19:17 Christof Schulze said the following: Hi, Oh, forgot a need to simply bump port revisions of all xorg driver ports. That's perhaps a little bit laborious, but doesn't require any special skills. Or did you have something else in mind? more than just laborious. It will break at least the Intel driver as intel is now GEM only which is not available on FreeBSD yet. What exactly will break this? Do you mean xorg-server-1.7.7 *requires* newer version of xf86-video-intel than what we have now in the ports? Because I don't have such an impression. -- Andriy Gapon ___ 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: xorg-server 1.7.7
On Mon, 08 Nov 2010 19:22:22 +0200 Andriy Gapon a...@icyb.net.ua wrote: on 08/11/2010 19:17 Christof Schulze said the following: Hi, Oh, forgot a need to simply bump port revisions of all xorg driver ports. That's perhaps a little bit laborious, but doesn't require any special skills. Or did you have something else in mind? more than just laborious. It will break at least the Intel driver as intel is now GEM only which is not available on FreeBSD yet. What exactly will break this? Do you mean xorg-server-1.7.7 *requires* newer version of xf86-video-intel than what we have now in the ports? Because I don't have such an impression. AFAIK the server version has no relevance to problems caused by Linux-centric driver development. I installed 1.7.7. on September 29th and didn't need to touch the installed (admittedly radeon) graphics driver. -- Gary Jennejohn ___ 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
