The current portage version of xxxterm-1.518 does not have a working plugin architecture and locks up the browser when attempting to play flash video. It is also impossible to control plugins at runtime, enabling and disabling them on a site-by-site basis. Since flash is necessary for certain key pages, and the ability to control plugins on a site-by-site basis is a key feature of xxxterm, I think a version bump is in order. The latest snapshot version (1.8.1, from last month) seems to work like a charm. In a local overlay, I simply renamed the 1.518 ebuild and things seemed to work fine. Note that this requires masking of the old version because 518 > 8. Reproducible: Always
(In reply to comment #0) > The current portage version of xxxterm-1.518 does not have a working plugin > architecture and locks up the browser when attempting to play flash video. It > is also impossible to control plugins at runtime, enabling and disabling them > on a site-by-site basis. > > Since flash is necessary for certain key pages, and the ability to control > plugins on a site-by-site basis is a key feature of xxxterm, I think a version > bump is in order. > > The latest snapshot version (1.8.1, from last month) seems to work like a > charm. > > In a local overlay, I simply renamed the 1.518 ebuild and things seemed to work > fine. Note that this requires masking of the old version because 518 > 8. > > Reproducible: Always Masking isn't the right way to deal with this tree-wide. Actually I don't know exactly what is the best way to deal with this kind of version scheme change.
There are also some new snapshots. Any progress here?
Created attachment 304031 [details] xxxterm-1.11.3.ebuild This is an .ebuild for the last (sic) version of xxxterm. According to its welcome message, "Beware that this is the final version that will use the xxxterm name. Moving forward the browser will be called xombrero. Details will soon appear on the https://opensource.conformal.com/wiki/xombrero Unfortunately scroogle has shut it's doors and due to that one has to edit search_string in ~/.xxxterm.conf. There are various examples in the configuration file. The authors of xxxterm are not in a position to suggest a search engine." In this particular .ebuild I applied the substitutions of the links to Scroogle to the corresponding links to DuckDuckGo for users not to end up with a non-working search engine. This version could be installed using emerge =xxxterm-1.11.3 Hope, it will be useful to somebody. Vladimir
I arrived here after looking for updating .xxxterm.conf, I have tried your ebuild and thank you very much for taking the time to create it. I will use version 1.11.3 for now, and open any bugs as required. For this bug report, I would say that a bump up the tree is justified as the user experience from 1.11.3 is IMO superior.
(In reply to comment #1) > Masking isn't the right way to deal with this tree-wide. Actually I don't > know exactly what is the best way to deal with this kind of version scheme > change. Any news here? How about mask it, remove from portage and then readd with updated version? ;) As noticed by Phill, there's a _huge_ difference in user experience in newer releases.
(In reply to comment #5) > (In reply to comment #1) > > Masking isn't the right way to deal with this tree-wide. Actually I don't > > know exactly what is the best way to deal with this kind of version scheme > > change. > > Any news here? How about mask it, remove from portage and then readd with > updated version? ;) > > As noticed by Phill, there's a _huge_ difference in user experience in newer > releases. Done. Using 1.1103 instead of 1.11.3 to make portage happy. +*xxxterm-1.1103 (17 Mar 2012) + + 17 Mar 2012; Rafael G. Martins <rafaelmartins@gentoo.org> + +xxxterm-1.1103.ebuild, xxxterm-9999.ebuild: + Version bump. 1.1103 == 1.11.3 (upstream). + (In reply to comment #3) > Created attachment 304031 [details] > xxxterm-1.11.3.ebuild > > This is an .ebuild for the last (sic) version of xxxterm. > According to its welcome message, > > "Beware that this is the final version that will use the xxxterm name. > Moving forward the browser will be called xombrero. > > Details will soon appear on the > https://opensource.conformal.com/wiki/xombrero > Unfortunately scroogle has shut it's doors and due to that one has to edit > search_string in ~/.xxxterm.conf. > There are various examples in the configuration file. > The authors of xxxterm are not in a position to suggest a search engine." > > In this particular .ebuild I applied the substitutions of the links to > Scroogle to the corresponding links to DuckDuckGo for users not to end up > with a non-working search engine. > > This version could be installed using > emerge =xxxterm-1.11.3 > > Hope, it will be useful to somebody. > > Vladimir I think I fixed the version issue. About the usage of google for searches, you should complain with upstream. I'll rename the package as soon as upstream renames it. Thanks!
Hello! I've just noticed that xxxterm still tries to use Scroogle by default which does not work at the moment and unlikely to work in the future as far as I know. That was the reason for me to add the corresponding lines in the .ebuild (see my attachment) to automatically change scroogle to DuckDuckGo by default. Would you please add those lines to the 1.1103 ebuild in the Portage tree? Thanks!
(In reply to comment #7) > Hello! > I've just noticed that xxxterm still tries to use Scroogle by default which > does not work at the moment and unlikely to work in the future as far as I > know. > That was the reason for me to add the corresponding lines in the .ebuild > (see my attachment) to automatically change scroogle to DuckDuckGo by > default. > > Would you please add those lines to the 1.1103 ebuild in the Portage tree? > > Thanks! Hi Vladimir, I'm not going to touch this thing now. I think I don't have the power to change any url in the software to something that isn't gentoo related, like I did for the default homepage. Please send a patch upstream to change the search engine. I'll be happy to apply it in our ebuild as soon as it reaches upstream's git. Thanks
