Seamonkey-2.7beta is available.
I am currently running 2.7b5 and have not had any problems since installing last week
majorfoo
Seamonkey-2.7 Beta
Re: Seamonkey-2.7 Beta
Final version of Seamonkey-2.7 is now available and it works without problems for me on Racy.majorfoo wrote:Seamonkey-2.7beta is available.
I am currently running 2.7b5 and have not had any problems since installing last week
majorfoo
[b]Classic Opera 12.16 browser SFS package[/b] for Precise, Slacko, Racy, Wary, Lucid, etc available[url=http://terryphillips.org.uk/operasfs.htm]here[/url] :)
- Digital_Dissident
- Posts: 25
- Joined: Tue 02 Mar 2010, 10:49
- Location: U.S.- E. Coast
2.7.2 is Current SeaMonkey, yet repos don't have past 1.x
http://www.seamonkey-project.org/
shows 2.7.2 as the current final version available for download.
(released Feb. 17, 2012)
Yet, I cannot find anything past 1.x in any of the repos.
(I am running Slacko 5.3.1 and updated the repos)
Can I download 2.7.2 from the SeaMonkey site without expecting trouble? (Dependency issues, etc.?)
shows 2.7.2 as the current final version available for download.
(released Feb. 17, 2012)
Yet, I cannot find anything past 1.x in any of the repos.
(I am running Slacko 5.3.1 and updated the repos)
Can I download 2.7.2 from the SeaMonkey site without expecting trouble? (Dependency issues, etc.?)
Re: 2.7.2 is Current SeaMonkey, yet repos don't have past 1.x
I am currently running Seamonkey 2.8 beta3 in Slacko 5.3.2.6 and not had any problems so far. I also ran this version in Slacko 5.3.2.4, same resultsDigital_Dissident wrote:http://www.seamonkey-project.org/
shows 2.7.2 as the current final version available for download.
(released Feb. 17, 2012)
Yet, I cannot find anything past 1.x in any of the repos.
(I am running Slacko 5.3.1 and updated the repos)
Can I download 2.7.2 from the SeaMonkey site without expecting trouble? (Dependency issues, etc.?)
Seamonkey 2.7.2
there is a pet available for Seamonkey 2.7.2 :
seamonkey-2.7.2-Saluki-i686.pet
download 21 MB
at
http://www.smokey01.com/saluki/pet_packages-saluki/
I have used it successfully to replace ver. 2.5 in Slacko 5.3.1 .
cheers
proebler
seamonkey-2.7.2-Saluki-i686.pet
download 21 MB
at
http://www.smokey01.com/saluki/pet_packages-saluki/
I have used it successfully to replace ver. 2.5 in Slacko 5.3.1 .
cheers
proebler
- Digital_Dissident
- Posts: 25
- Joined: Tue 02 Mar 2010, 10:49
- Location: U.S.- E. Coast
Re: Seamonkey 2.7.2
First, a belated thanks for the replies.
(I know what it can feel like to not receive any acknowledgment for trying to be helpful, so I apologize for taking so long to get back to this thread.)
I must ask, wouldn't it be much better (and more secure) to handle package management more in line with the way mainstream distros do: official repositories maintained with updated packages as they become available, added only after approval and authentication from the development team? (This issue of package management has, I'm sorry to say, been one of several factors why despite appreciating the idea and many aspects of Puppy, I have yet to try a release that didn't quickly turn-out to cause me too much trouble and aggravation to be worthwhile to stay with. )
I realize that this is really a topic for a separate thread unto itself, though.
( Let me note that I do respect the dedication and commitment of Mr. Kauler and the many others who contribute to the Puppy project, and many of the goals and principals that it embraces.)
(I know what it can feel like to not receive any acknowledgment for trying to be helpful, so I apologize for taking so long to get back to this thread.)
No signatures or even checksums?proebler wrote:there is a pet available for Seamonkey 2.7.2 :
seamonkey-2.7.2-Saluki-i686.pet
download 21 MB
at
http://www.smokey01.com/saluki/pet_packages-saluki/
I have used it successfully to replace ver. 2.5 in Slacko 5.3.1 .
cheers
proebler
I must ask, wouldn't it be much better (and more secure) to handle package management more in line with the way mainstream distros do: official repositories maintained with updated packages as they become available, added only after approval and authentication from the development team? (This issue of package management has, I'm sorry to say, been one of several factors why despite appreciating the idea and many aspects of Puppy, I have yet to try a release that didn't quickly turn-out to cause me too much trouble and aggravation to be worthwhile to stay with. )
I realize that this is really a topic for a separate thread unto itself, though.
( Let me note that I do respect the dedication and commitment of Mr. Kauler and the many others who contribute to the Puppy project, and many of the goals and principals that it embraces.)