Fedora Weekly News 269
by Pascal Calarco
* 1 Fedora Weekly News Issue 269
o 1.1 Announcements
+ 1.1.1 Fedora Announcement News
# 1.1.1.1 Changes to the Packaging Guidelines
+ 1.1.2 Fedora Development News
# 1.1.2.1 Beta change freeze
# 1.1.2.2 Fedora 15 schedule to slip an additional week
+ 1.1.3 Fedora Events
# 1.1.3.1 Upcoming Events (March - May 2011)
# 1.1.3.2 Past Events
# 1.1.3.3 Additional information
o 1.2 Fedora In the News
+ 1.2.1 Red Hat Proves That Open Source Is Good for Business (PC World)
o 1.3 Ambassadors
+ 1.3.1 Welcome New Ambassadors
+ 1.3.2 Summary of traffic on Ambassadors mailing list
+ 1.3.3 Summary of events reported on Ambassadors mailing list
+ 1.3.4 Summary of traffic on FAmSCo mailing list
o 1.4 QualityAssurance
+ 1.4.1 Test Days
+ 1.4.2 Anaconda testing
+ 1.4.3 GNOME Tweak Tool testing
+ 1.4.4 Fedora 15 Beta preparation
+ 1.4.5 Improving pre-release download page
o 1.5 Security Advisories
+ 1.5.1 Fedora 15 Security Advisories
+ 1.5.2 Fedora 14 Security Advisories
+ 1.5.3 Fedora 13 Security Advisories
o 1.6 LATAM Fedora!
+ 1.6.1 Ruby Capítulo 2 : Una clase algo más completa
# 1.6.1.1 Constantes vs variables
# 1.6.1.2 El poder de herencia
# 1.6.1.3 Espacios de nombres
# 1.6.1.4 Herencia múltiples vs Mixins
* 1.6.1.4.1 mixin_module.rb
- Fedora Weekly News Issue 269 -
Welcome to Fedora Weekly News Issue 269[1] for the week ending March 30, 2011. What follows are some highlights from this issue.
This issue begins with announcements from the Fedora Project, including changes to the packaging guidelines and an additional week slip of the Fedora 15 release date. One article for Fedora In the News this week from PC World on Red Hat's financial success. In Ambassador news, details on new members of the team, a summary of discussion on the Ambassador and FAmSCo lists, and a couple event reports. In Quality Assurance news, details on the latest and upcoming Test Days on power management, printing and ABRT, as well as various reports leading up to the Fedora 15 beta release. Security Advisories brings us current with the security-related package releases this past week for Fedora 13, 14 and 15, and in our Latin American beat this week, a second installment of Guillermo Gomez's Ruby Primer, in Spanish. Enjoy!
An audio version of some issues of FWN - FAWN - are available! You can listen to existing issues[2] on the Internet Archive. If anyone is interested in helping spread the load of FAWN production, please contact us!
If you are interested in contributing to Fedora Weekly News, please see our 'join' page[3]. We welcome reader feedback: news(a)lists.fedoraproject.org
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. ↑ http://fedoraproject.org/wiki/FWN/Issue269
2. ↑ http://www.archive.org/search.php?query=subject%3A%22FWN%22
3. ↑ http://fedoraproject.org/wiki/NewsProject/Join
-- Announcements --
In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].
Contributing Writer: Pascal Calarco
1. ↑ http://lists.fedoraproject.org/pipermail/announce/
2. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/
3. ↑ http://fedoraproject.org/wiki/Events
--- Fedora Announcement News ---
The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at[1]
1. ↑ https://admin.fedoraproject.org/mailman/listinfo/announce
---- Changes to the Packaging Guidelines ----
Tom 'Spot' Callaway announced[1],
"Here are the changes to the Fedora Packaging Guidelines for this week:
The Packaging:PHP guidelines have been updated to reflect that PEAR documentation provided by upstream are installed in %{pear_docdir}, should stay there, and must be marked as %doc.
Additionally, the definition of pear_docdir has been defined as %{_docdir}/pear.
https://fedoraproject.org/wiki/Packaging:PHP
---
The Java guidelines have been updated to add information and sample template for Maven 3 (Fedora 15+).
https://fedoraproject.org/wiki/Packaging:Java
---
These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).
Many thanks to Remi Collet, Stanislav Ochotnicky, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.
As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here [2]
Thanks,
~spot"
1. ↑ http://lists.fedoraproject.org/pipermail/announce/2011-March/002942.html
2. ↑ http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
--- Fedora Development News ---
The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.
Acceptable Types of Announcements
* Policy or process changes that affect developers.
* Infrastructure changes that affect developers.
* Tools changes that affect developers.
* Schedule changes
* Freeze reminders
Unacceptable Types of Announcements
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above
1. ↑ https://admin.fedoraproject.org/mailman/listinfo/devel-announce
---- Beta change freeze ----
Dennis Gilmore announced[1],
"Hi All a heads up that change freeze for the Fedora 15 Beta is Tuesday April 5th. After this point only accepted blocker bugs will be pulled in. Please limit your changes to try and avoid unintended breakages.
thanks
Dennis"
1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000773...
---- Fedora 15 schedule to slip an additional week ----
Jared K. Smith announced[1]
"The Fedora 15 development cycle is well under way, and making good progress. Yesterday I met[1] with Release Engineering, QA, the Fedora Program Manager, and we decided that in order to accommodate some late-breaking changes, we're going to need to slip the Fedora 15 release schedule by a week in order to have adequate time to do proper testing of the candidate images before the Beta. This slip will affect the entire Fedora 15 development cycle, as shown in the chart below:
o F15 Devel Start 2010-11-02
o Feature Submission Deadline 2011-01-25
o Feature Freeze 2011-02-08
o Branch From Rawhide 2011-02-08
o Software String Freeze 2011-02-15
o Alpha Change Deadline 2011-02-15
o Alpha Release 2011-03-08
N O W -----------------------
o Software Translation Deadline 2011-04-05
o Beta Change Deadline 2011-04-05
o Features 100% Complete 2011-04-05
o Beta Release 2011-04-19
o Final Change Deadline 2011-05-09
o Compose RC 2011-05-10
o GA 2011-05-24
Robyn Bergeron has also kindly updated the complete break-out of the Fedora release schedule, which is available[2]. If you have any questions or concerns, please don't hesitate to let me know.
-- Jared Smith Fedora Project Leader "
1. ↑ http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000772...
2. ↑ http://rbergero.fedorapeople.org/schedules/f-15/
--- Fedora Events ---
The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!
---- Upcoming Events (March - May 2011) ----
* North America (NA)[1]
* Central & South America (LATAM): [2]
* Europe, Middle East, and Africa (EMEA)[3]
* India, Asia, Australia (India/APJ)[4]
1. ↑ http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29
2. ↑ http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_2
3. ↑ http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_3
4. ↑ http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_4
---- Past Events ----
Archive of Past Fedora Events[1]
1. ↑ http://fedoraproject.org/wiki/FedoraEvents/PastEvents
---- Additional information ----
* Reimbursements -- reimbursement guidelines.
* Budget -- budget for the current quarter (as distributed by FAMSCo).
* Sponsorship -- how decisions are made to subsidize travel by community members.
* Organization -- event organization, budget information, and regional responsibility.
* Event reports -- guidelines and suggestions.
* LinuxEvents -- a collection of calendars of Linux events.
-- Fedora In the News --
In this section, we cover news from the trade press and elsewhere that is re-posted to the Fedora Marketing list[1].
http://fedoraproject.org/wiki/Marketing
Contributing Writer: Pascal Calarco
1. ↑ http://lists.fedoraproject.org/pipermail/marketing/
--- Red Hat Proves That Open Source Is Good for Business (PC World) ---
Rahul Sundaram forwarded[1] a posting on Red Hat's financial success:
"Critics of free and open source software are fond of making the argument that software must be locked up, patented and jealously guarded if it is to serve as the basis for a successful business. Well, Red Hat just refuted such claims in a big way this week with its fourth quarter earnings report, which blew away analysts' expectations and placed the company well on track for billion-dollar revenues in the upcoming year."
Based in North Carolina, Red Hat is the company behind both the Fedora and the Red Hat Enterprise Linux (RHEL) Linux distributions. Fedora is the free, community version of the software, while RHEL is sold as acommercial product with support and services."
The full article is available[2].
1. ↑ http://lists.fedoraproject.org/pipermail/marketing/2011-March/013758.html
2. ↑ http://www.pcworld.com/businesscenter/article/223346/red_hat_proves_that_...
-- Ambassadors --
This section covers the news surrounding the Fedora Ambassadors Project[1].
Contributing Writer: Sankarshan Mukhopadhyay
1. ↑ http://fedoraproject.org/wiki/Ambassadors
--- Welcome New Ambassadors ---
This week the Fedora Ambassadors Project had a couple of new members joining.
Everton Cardoso from Brazil mentored by Daniel Bruno
--- Summary of traffic on Ambassadors mailing list ---
Christoph Wickert raised [1] some questions regarding the budget [2] Max Spevack provided [3] actual figures from the expenses. David Nalley mentioned [4] that some of the issues raised in the mail were also part of the Board IRC meeting and, discussions were ongoing as the same was an agenda item in the upcoming Board meeting.
Onyeibo Oku asked [5] if there was an existing print-ready, A5 sized booklet covering the basics of Fedora for handing out at events. Zoltan Hopper responded [6] about a scratch document available at the Marketing Page. There was further discussion around the difference between a Quick-Start and a Handbook [7] and the possibility of building a Quick Start Guide [8] based upon the SXSW Materials [9]
Christoph Wickert posted [10] Minutes of EMEA Ambassadors Meeting [11] The thread [12] had additional discussion around allocation of funds under budget line items and, expense planning based on projected needs. The decision making process within FAmSCo was also discussed.
David Ramsey posted [13] meeting notes [14] from the APAC Ambassadors meeting on 2011-03-19
David Ramsey informed [15] about an upcoming Power Management Test Day [16] and subsequently posted [17] about the Printing and ABRT Retrace Server Test Days
Máirín Duffy asked [18] if there was a group photograph from a recent event with the aim of updating the FUDCon Zurich group phot that is on fedoraproject.org page
Christoph Wickert posted [19] a 'Last Call for Orders" for F14 media for any event at EMEA and added a link to the Inventory [20] for helping to search for the nearest anchor point
Pierros Papadeas posted [21] Meeting Minutes for FAmSCo meeting of 2011-03-26
Buddhika Kurera requested help [22] in finding a co-speaker for CLT2011
Paul Mellors posted [23] about an idea for a documentary [24] similar to "Revolution OS"
Adam Miller put out a last call for funding for Texas Linux Fest 2011 [25]
1. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017242.html
2. ↑ https://fedoraproject.org/wiki/FAmSCo_report_2011-02
3. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017245.html
4. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017317.html
5. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017252.html
6. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017253.html
7. ↑ http://fedoraproject.org/wiki/User:Sankarshan/FedoraHandbook
8. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017261.html
9. ↑ https://fedoraproject.org/wiki/Design/SXSW_Materials
10. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017264.html
11. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2011-03-23/emea_ambassado...
12. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/thread.ht...
13. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017265.html
14. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2011-03-19/apac.2011-03-1...
15. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017267.html
16. ↑ https://fedoraproject.org/wiki/Test_Day:2011-03-24
17. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017312.html
18. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017282.html
19. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017293.html
20. ↑ https://fedorahosted.org/emea-swag-tracking/wiki/Inventory
21. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017296.html
22. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017299.html
23. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017314.html
24. ↑ https://fedoraproject.org/wiki/Fedora_Documentary
25. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017310.html
--- Summary of events reported on Ambassadors mailing list ---
Christoph Wickert reported [1] on the Chemnitzer Linuxtage event with more details about undertaking similar tasks using different distributions.
Fabian Affolter summarized [2] all the CLT2011 reports
1. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017241.html
2. ↑ http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017284.html
--- Summary of traffic on FAmSCo mailing list ---
Pierros Papadeas posted [1] the Agenda for the FAmSCo meeting of 2011-03-26 [2]
Joerg Simon, as the Fedora Ambassador Membership Administrator, informed FAmSCo [3] about existing continuous violations of Fedora Ambassador Conduct [4] Follow-up discussions happened on the ticket and the thread [5]
1. ↑ http://lists.fedoraproject.org/pipermail/famsco/2011-March/000736.html
2. ↑ https://fedoraproject.org/wiki/FAmSCo_agenda#2011-3-26_agenda
3. ↑ http://lists.fedoraproject.org/pipermail/famsco/2011-March/000737.html
4. ↑ https://fedorahosted.org/famsco/ticket/156
5. ↑ http://lists.fedoraproject.org/pipermail/famsco/2011-March/thread.html#737
-- QualityAssurance
In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].
Contributing Writer: Adam Williamson
1. ↑ http://fedoraproject.org/wiki/QA
2. ↑ http://fedoraproject.org/wiki/QA/Join
--- Test Days ---
Thursday 2011-03-24 was power management Test Day[1]. The event produced a great turnout of testers who provided results on a wide range of hardware, and the developers are already looking at the bugs filed. Thanks to everyone who came out to help.
This Tuesday, 2011-03-29, was printing Test Day[2]. The turnout was a little smaller than we hoped, but the testers who did come managed to find lots of bugs, and Fedora's printing maintainer, Tim Waugh, was very happy with all the results.
This Thursday, 2011-03-31, will be ABRT Test Day[3]. As well as checking that ABRT (Fedora's automated crash report tool) is working as expected for Fedora 15, we'll be testing out a big new feature, the retrace server[4]. This allows you to submit crash reports to a remote server which will generate the backtrace - avoiding the need for you to download and install often large debuginfo packages in order to submit reports. Please come along and help us test this exciting new feature!
There is currently no Test Day planned for next Thursday, 2011-04-07. Take the day off!
1. ↑ http://fedoraproject.org/wiki/Test_Day:2011-03-24
2. ↑ http://fedoraproject.org/wiki/Test_Day:2011-03-29
3. ↑ http://fedoraproject.org/wiki/Test_Day:2011-03-31_ABRT_Retrace_Server
4. ↑ http://fedoraproject.org/wiki/Features/RetraceServer
--- Anaconda testing ---
James Laska requested testing of an installer image which included updated versions of anaconda and lorax that needed testing before being approved as stable updates[1]. Several testers responded, and the updates were soon approved.
1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-March/098018.html
--- GNOME Tweak Tool testing ---
Michel Salim announced that GNOME Tweak Tool, an application for tweaking various advanced settings in GNOME 3, was now available for testing[1]. Several group members thanked Michel for the announcement and provided feedback on the tool.
1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-March/098107.html
--- Fedora 15 Beta preparation ---
The third Beta blocker/nice-to-have review meeting took place on 2011-03-25[1], and the team worked through the full list of proposed Beta blocker and nice-to-have bugs. The first test compose was scheduled for Tuesday 2011-03-22, but could not be completed on that day due to various outstanding bugs and the lack of the planned NetworkManager 0.9 packages. At a special release schedule meeting on Wednesday 2011-03-23[2], the QA and release engineering teams, and the Fedora Project Leader, agreed that the late arrival of NetworkManager 0.9 justified a one week slip in the release schedule. The first test compose was then set for Tuesday 2011-03-29.
1. ↑ http://meetbot.fedoraproject.org/fedora-bugzappers/2011-03-25/f-15-beta-b...
2. ↑ http://meetbot.fedoraproject.org/fedora-meeting/2011-03-23/fedora-meeting...
--- Improving pre-release download page ---
Tim Flink passed on some feedback[1] he had received from a new tester who had downloaded a pre-release and asked some questions in the #fedora IRC channel, which does not handle pre-release issues. He suggested that it would be a good idea to add some text to the pre-release download page[2] explaining the right places to go to post feedback and get help with pre-release issues. Jóhann Guemundsson and Adam Williamson both suggested filing a request with the websites team, and Tim reported[3] that he had filed a ticket[4].
1. ↑ http://lists.fedoraproject.org/pipermail/test/2011-March/098160.html
2. ↑ http://fedoraproject.org/get-prerelease
3. ↑ http://lists.fedoraproject.org/pipermail/test/2011-March/098173.html
4. ↑ http://fedorahosted.org/fedora-websites/ticket/45
-- Security Advisories --
In this section, we cover Security Advisories from fedora-package-announce from the past week.
http://lists.fedoraproject.org/pipermail/package-announce
Contributing Writer: Pascal Calarco
--- Fedora 15 Security Advisories ---
* libxml2-2.7.8-6.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0570...
* logrotate-3.7.9-8.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0569...
* asterisk-1.8.3.2-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0569...
* php-doctrine-Doctrine-1.2.4-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0569...
* roundcubemail-0.5.1-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0569...
* nss-3.12.9-14.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0568...
* subversion-1.6.16-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0567...
* libcgroup-0.37.1-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0567...
* phpMyAdmin-3.3.10-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0567...
* maniadrive-1.2-29.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0566...
* php-eaccelerator-0.9.6.1-6.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0566...
* php-5.3.6-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0566...
--- Fedora 14 Security Advisories ---
* phpMyAdmin-3.3.10-1.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0570...
* wordpress-3.1-1.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0570...
* gnash-0.8.9-1.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0567...
* libcgroup-0.36.2-6.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0566...
* krb5-1.8.2-9.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
--- Fedora 13 Security Advisories ---
* phpMyAdmin-3.3.10-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0570...
* wordpress-3.1-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0569...
* gnash-0.8.9-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0567...
* krb5-1.7.1-18.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
-- LATAM Fedora! --
LATAM Fedora is a regular column of Spanish language contributions around open source software. It is our first expansion into incorporating foreign language content into FWN.
This week's contribution is from Guillermo Gómez, a second installment primer on Ruby. Enjoy!
---- Ruby Capítulo 2 : Una clase algo más completa ----
Siguiendo nuestra secuencia al estilo tutorial, en esta edición vamos a completar un poco más nuestras clases, introduciresmo los conceptos de métodos y variables de clase.
Una variable de clase es una variable compartida de la clase misma. Sólo existe una copia de una variable de clase en particular para una clase dada. Los nombres de las variables de clase comienzan con @@ tal como en @@reproducciones.
1 class Cancion
2 @@reproducciones = 0
3
4 def Cancion.reproducciones
5 @@reproducciones
6 end
7
8 def reproducir
9 @@reproducciones =+ 1
10 end
11 end
A diferencia de las variables de instancia y variables globales, las variables de clase deben se inicializadas antes de poder ser utilizadas, usualmente se hace con una declaración simple en el cuerpo de la definición de la clase. En el código anterior igualmente se ha introducido el concepto de método de clase. Un método de clase es un método que no necesita que se instancie la clase para ser invocado, es decir, "son métodos propios de la clase y no de sus objetos".
Su utilidad es obvia en el ejemplo, se quiere saber cuántas reproducciones se han hecho en total en nuestro reproductor de música. Esta información no es específica a una canción en particular, es decir, no es sujeto de las instancias sino de la clase misma. La diferencia al momento de declarar el método de clase es que debe anteponer el nombre de la clase al método, tiene dos opciones, o usar explícitamente Cancion, o self. El uso de *self" da mayor flexibilidad ya que permite cambiar el nombre de la clase sin mayores traumas.
1 class Cancion
2 @@reproducciones = 0
3
4 def self.reproducciones
5 @@reproducciones
6 end
7
8 def reproducir
9 @@reproducciones =+ 1
10 end
11 end
---- Constantes vs variables ----
Las variables y constantes en Ruby mantienen referencias a objetos. Las variables no poseen un tipo intrínseco, a cambio el tipo es únicamente definido por los mensajes a los que responde el objeto referenciado.
Una constante en Ruby también es una referencia a un objeto. Las constantes son creadas cuando son asignadas por primera vez, a diferencia de otros lenguajes Ruby le permite alterar el valor de las constantes si bien ello provocará un mensaje de alerta. En general usted no debe alterar una constante en tiempo de ejecución y debería evitarlo a toda costa.
1 >> MI_CONSTANTE = 1
2 => 1
3 >> MI_CONSTANTE = 2
4 (irb):23: warning: already initialized constant MI_CONSTANTE
5 => 2
Note como las constantes pueden declararse dentro de la definición de clase lo que nos lleva a la definición de constante de clase y a la noción de espacios de nombres por la forma en que nos referimos a dichas constantes.
1 class Cancion
2 VERSION="1.0"
3 end
1 >> Cancion::VERSION
2 => "1.0"
3 >> VERSION
4 => "1.8.7"
Note que VERSION no referencia ni colisiona con Cancion::VERSION.
---- El poder de herencia ----
Tal vez el santo grial de la programación es el principio DRY, "Don Repeat Yourself". Una forma de evitar repetirse, es escribir código reusable, cada vez que estamos escribiendo nuevo código y tenemos esa sensación de deja-vu de que ya esto lo hicimos una vez en el pasado, es porque no estamos reusando nuestro código de forma inteligente. En POO la herencia es una excelente forma de mantener el código reusable sin mayores repeticiones.
La herencia le permite crear clases que sean refinamientos o especializaciones de otra clase. Por ejemplo, y siguiendo el ejemplo de Cancion en nuestro reproductor de música ahora a alguien se le ocurrió que sería interesante que se incluyera el soporte para canciones de tipo Karaoke. La única diferencia con las otras canciones es que las canciones Karaoke tienen asociadas la letra de la canción en conjunto con infomación de sincronización para reproducir las letras del Karaoke en nuestro flamante reproductor ahora con una gran pantalla de video.
1 class Karaoke < Cancion
2 def initialize(nombre, artista, duracion, letra)
3 super(nombre, artista, duracion)
4 @letra = letra
5 end
6 end
El "< Cancion" en la definición de la clase le indica a Ruby que Karaoke es un subclase de Cancion, o en dirección opuesta, Cancion es la superclase de Karaoke. De esta forma la clase hija hereda todos los métodos y declaraciones de variables de su padre. Al invocar un método sobre un objeto o clase, Ruby defiere su ubicación hasta el momento de ejecución, en dicho momento Ruby primero mira en la clase para determinar si existe el método invocado, si no es así, intenta en el padre, y así atravesando todos los ancestros de la clase hasta ubicar el método invocado. Si se acaban los ancestros donde buscar, Ruby ejecuta una acción especial que puede ser interceptada si se desea Object#method_missing, si no, produce un error.
Cada clase especializada maneja sus detalles, para el resto se utiliza super, es decir, el método del padre o de su ancestro. De esta forma, por ejemplo, en nuestra definición de Karaoke#initialize dejamos que la inicialización de todo lo común a Cancion ocurra igual que antes por medio de la llamada a super con los respectivos parámetros necesarios, luego inicializamos los datos específicos a nuetras clase Karaoke.
---- Espacios de nombres ----
En la medida que escriba programas Ruby cada vez más grandes, usted naturalmente se encontrará con código reusable, librerías de rutinas relacionadas entre sí por ejemplo. Usted deseará separar dicho código en distintos archivos separados de tal forma que el contenido pueda ser reusado entre diferentes programas Ruby. Frecuentemente este código será organizado en clases.
Otras veces ello simplemente no es conveniente o no aplica, son un grupo de métodos que desea reusar, usted puede simplemente colocarlos en un archivo y cargar dicho archivo en su programa con load o require. Esto funciona pero tiene un problema, digamos que se crea una librería para cocinar con los métodos calentar , mezclar, amasar en un archivo cocina.rb y otra librería para atletas con los métodos calentar, correr, descansar en el archivo atleta.rb. Si carga ambos archivos uno después del otro, simplemente el método calentar colisiona y sólo el más recientemente cargado tendrá la definicón actual del método, el otro simplemente será olvidado, en resumen la colisión en los nombres es el problema.
La respuesta es el mecanismo de modulos. Los modulos definen un espacio de nombres en donde sus métodos y constantes pueden aplicar sin tener que preocuparse en colisionar con otros métodos y constantes:
1 module Cocina
2 ESCUELA="Latinoamericana"
3 def Cocina.calentar(x)
4 # Se espera que x sea un valor númerico para representar temperatura en oC
5 # ..
6 end
7 ...
8 end
9
10 module Atleta
11 ESCUELA="Simón Bolívar"
12 def Atleta.calentar(t)
13 # Se espera que t sea un valor numérico que represente tiempo en segundos
14 # ..
15 end
16 end
1 >> Cocina::ESCUELA
2 => "Latinoamericana"
3 >> Atleta::ESCUELA
4 => "Simon Bolivar"
5 >> include Atleta
6 => Object
7 >> Atleta.calentar(1000)
8 calentando 1000 segundos
9 => nil
10 >> include Cocina
11 => Object
12 >> Cocina.calentar(10)
13 => 10
Ahora entonces tiene mucho menos probabilidades de provocar colisiones, note que debe cargar el código, y luego include para usar las funcionalidades del módulo.
---- Herencia múltiples vs Mixins ----
Algunos lenguajes orientados a objetos, tales como C++, soportan herencia múltiple en donde una clase puede tener más de una superclase heredando funcionalidad de cada una de ellas. Si bien potente, esta técnica puede ser peligrosa ya que la jerarquía puede tener ambigüedades. Otros lenguajes como java y C# soportan sólo herencia simple. Si bien más limpia y simple, la herencia simple también tiene sus desventajas, en la realidad los objetos heredan atributos de múltiples fuentes en el mundo real.
Ruby ofrece una alternativa interesante y poderosa que le ofrece la simplicidad de la herencia simple y el poder la herencia múltiple. Una clase Ruby tiene una única clase padre, en consecuencia Ruby es un lenguaje con herencia simple, sin embargo, las clases Ruby pueden incluir la funcionalidad de cualquier cantidad de mixins (un mixin es una especie de definición parcial de clase). Nuevamente dejemos que Ruby hable, creemos nuestro archivo con la definición de módulo y un par de clases tontas que lo usen como mixin:
---- mixin_module.rb ----
1 module Debug
2 def quien_soy?
3 "#{self.class.name} (\##{self.objet_id}): #{self.to_s}"
4 end
5 end
6
7 class Cocina
8 include Debug
9 def estilo
10 puts "Italiana"
11 end
12 end
13
14 class Nevera
15 include Debug
16 def capacidad
17 puts "150 pies cúbicos"
18 end
19 end
Si ahora cargamos dichas definiciones de módulo y clases en irb, podemos evidenciar y experimentar con el uso de los mixins (note que le voy a pasar la forma de hacerlo):
1 $ irb
2 >> load 'mixin_module.rb'
3 => true
4 >> nevera = Nevera.new
5 => #<Nevera:0xb7587b38>
6 >> cocina = Cocina.new
7 => #<Cocina:0xb7585c5c>
8 >> nevera.quien_soy?
9 => "Nevera (#-609469028): #<Nevera:0xb7587b38>"
10 >> cocina.quien_soy?
11 => "Cocina (#-609472978): #<Cocina:0xb7585c5c>"
Bien, es todo por hoy, nos recontraremos en un tercer capítulo dedicado a métodos en una próxima edición de esta serie dedicada a aprender Ruby.
Este artículo se mantiene en línea en gomix.fedora-ve.org para posibles mejoras y erratas.
Guillermo Gómez
13 years, 2 months
FWN 269
by Pascal Calarco
is almost complete at:
https://fedoraproject.org/wiki/FWN/Issue269
Rashadul, how are things looking for the announcements beat? If you're in a crunch, just let me know and I can pull that together for this issue.
Thanks to Adam, Sankarshan for your beats!
- pascal
13 years, 2 months
QA in for 269
by Adam Williamson
getting in ahead of schedule, I have QA beat in for this week now.
thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 2 months
Fedora Weekly News 268
by Pascal Calarco
* 1 Fedora Weekly News Issue 268
o 1.1 Announcements
+ 1.1.1 Fedora Announcement News
# 1.1.1.1 Fedora accepted in to Google Summer of Code 2011!
# 1.1.1.2 [Guidelines Change] Changes to the Packaging Guidelines
+ 1.1.2 Fedora Development News
# 1.1.2.1 Your package translation
+ 1.1.3 Fedora Events
# 1.1.3.1 Upcoming Events (Dec 2010 - Feb 2011)
# 1.1.3.2 Past Events
# 1.1.3.3 Additional information
o 1.2 Marketing
+ 1.2.1 MMM. Almost as tasty as a beefy miracle... your weekly delicious Marketing Meeting Minutes are here!
+ 1.2.2 SxSW photobooth awesomeness and its future
o 1.3 Fedora In the News
+ 1.3.1 Tim Burke: Ext4 Is Not Going Anywhere Any Time Soon (muktware.com)
+ 1.3.2 Linux shakedown: Testing both GNOME 3 and Fedora 15 (ZDNetAsia.com)
+ 1.3.3 Fedora 15 vs Ubuntu Natty Narwhal – The Battle for Your Next Desktop (maketecheasier.com)
+ 1.3.4 Using SELinux and iptables Together (Linux.com)
+ 1.3.5 Out with Windows 2000, in with Fedora 14, part 2 (ZDNet UK)
+ 1.3.6 Speedy 'Wonder Patch' Debuts in New Linux Kernel (PC World)
+ 1.3.7 Fedora shows off Gnome 3.0 (mybroadband.com South Africa)
+ 1.3.8 Fedora 15 alpha debuts GNOME 3, adds cloud appliance builder (DesktopLinux.com)
+ 1.3.9 My Wife Loves Gnome 3 (muktware.com)
+ 1.3.10 Playing With Fire, Fedora 15 and Gnome 3 (muktware.com)
o 1.4 Ambassadors
+ 1.4.1 Welcome New Ambassadors
+ 1.4.2 Summary of traffic on Ambassadors mailing list
+ 1.4.3 Summary of events reported on Ambassadors mailing list
+ 1.4.4 Summary of traffic on FAmSCo mailing list
o 1.5 QualityAssurance
+ 1.5.1 Test Days
+ 1.5.2 Release criteria revisions
+ 1.5.3 Nightly builds via Koji
+ 1.5.4 QA group governance
+ 1.5.5 Fedora 15 Beta preparation
o 1.6 Security Advisories
+ 1.6.1 Fedora 15 Security Advisories
+ 1.6.2 Fedora 14 Security Advisories
+ 1.6.3 Fedora 13 Security Advisories
o 1.7 LATAM Fedora!
+ 1.7.1 SOX
# 1.7.1.1 Agregando Soporte mp3 y m4a
# 1.7.1.2 Agregar soporte recompilando el Source RPM (SRPM)
* 1.7.1.2.1 Requisitos
# 1.7.1.3 Construcción e Instalación del RPM
+ 1.7.2 Convertir mp3
- Fedora Weekly News Issue 268 -
Welcome to Fedora Weekly News Issue 268[1] for the week ending March 23, 2011. What follows are some highlights from this issue.
Our issue opens with announcements, including details on Fedora being accepted into the 2011 Summer of Code, as well as notice of some changes to the packaging guidelines. We're looking for a permanent writer for the Marketing beat, but we have a short beat this week that includes weekly team meeting minutes and some thoughts on expanding the SXSW Fedora photobooth to other FAmNA events. This week's In the News beat has a whopping ten articles on Fedora 15, Gnome 3 and other topics, and Ambassadors brings us current on happenings in that team as well as FAmSCo. In QA news, details on this past week's Test Day on preupgrade, today's Power Management Test Day, and next week's ABRT Test Day as well as other working on Fedora 15. Security Advisories offers the latest security-related packages for Fedora 13-15, and our issue finishes up with another LATAM installment of Spanish FLOSS goodness from Guillermo Gomez, this week on the audio manipulation package, SOX. Read on!
An audio version of some issues of FWN - FAWN - are available! You can listen to existing issues[2] on the Internet Archive. If anyone is interested in helping spread the load of FAWN production, please contact us!
If you are interested in contributing to Fedora Weekly News, please see our 'join' page[3]. We welcome reader feedback: news(a)lists.fedoraproject.org
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. http://fedoraproject.org/wiki/FWN/Issue268
2. http://www.archive.org/search.php?query=subject%3A%22FWN%22
3. http://fedoraproject.org/wiki/NewsProject/Join
-- Announcements --
In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].
Contributing Writer: Pascal Calarco
1. http://lists.fedoraproject.org/pipermail/announce/
2. http://lists.fedoraproject.org/pipermail/devel-announce/
3. http://fedoraproject.org/wiki/Events
--- Fedora Announcement News ---
The announcement list is always exclusive for the Fedora Community. Please, visit the past announcements at[1]
1. https://admin.fedoraproject.org/mailman/listinfo/announce
---- Fedora accepted in to Google Summer of Code 2011! ----
Ryan Rix on Sat Mar 19 06:45:46 UTC 2011 announced[1],
"Heya folks :)
So... after a year's hiatus, Fedora's been accepted in to Google's Summer of Code program for summer 2011!
If you're a university student looking for a job this summer, start thinking about some awesome idea that you'd like to make happen in Fedora this summer. Applications will open March 28, so start talking with developers in IRC and mail, and find something awesome to do! We have a list of some ideas at: [2] but don't limit yourself to that list. Find a mentor, and make your idea happen!
Mentors should apply to be a mentor[3] in Google's Melange instance. be inviting those who are listed on the Ideas page. We've still some work to do before the student applications open, some scaffolding to build, and some things to decide, so please join in. I'll be sending mentors more information soon.
we're listed as The Fedora Project
Congratulations, everyone, for the Awesome we're doing!"
1. http://lists.fedoraproject.org/pipermail/announce/2011-March/002939.html
2. http://fedoraproject.org/wiki/Summer_coding_ideas_for_2011
3. http://www.google-melange.com/gsoc/org/apply_mentor/google/gsoc2011
---- [Guidelines Change] Changes to the Packaging Guidelines ----
Tom Callaway on Tue Mar 22 01:40:43 UTC 2011 announced[1],
"Here are the latest set of changes to the Fedora Packaging Guidelines:
---
The Emacs packaging guidelines were updated to handle cases where a package's principal functionality does not require (X)Emacs, but the package also includes some auxiliary Elisp files to provide support for the package in (X)Emacs.
[2]
---
The Scriptlet Snippets section dealing with the order that scriptlets are invoked has been updated to include %trigger scripts.
[3]
---
A subsection was added to the Packaging Guidelines section on Filesystem Layout in which it is made explicit that binaries in /bin or /sbin must NOT depend on any libraries in /usr/lib or /usr/lib64.
[4]
---
The section on Epochs was improved, and clarifying language about Epoch use in Requires was added to the Packaging Guidelines.
[5] [6]
---
New guidelines were added covering the packaging of Ada programs. [7]
---
The section on Boostrapping in the Treatment of Bundled Libraries page in the Packaging Guidelines has been amended to add the following:
Packages which are built in such a bootstrapping mode must not be tagged for a final release (or pushed as an update for any stable release). FPC will track the progress of approved bootstrapping exceptions via the ticket requesting the bootstrap bundling exception.
[8]
---
Macro forms of system executables (such as %{__rm}) should not be used except when there is a need to allow the location of those executables to be configurable.
[9]
---
These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).
Many thanks to Hans Niedermann, Jonathan Underwood, Pavel Zhukov, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.
As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here: [10]"
1. http://lists.fedoraproject.org/pipermail/announce/2011-March/002940.html
2. https://fedoraproject.org/wiki/Packaging:Emacs
3. https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Orde...
4. https://fedoraproject.org/wiki/Packaging:Guidelines#Binaries_in_.2Fbin_an...
5. https://fedoraproject.org/wiki/Packaging:Guidelines#Use_of_Epochs
6. https://fedoraproject.org/wiki/Packaging:Guidelines#Requires
7. https://fedoraproject.org/wiki/Packaging:Ada
8. https://fedoraproject.org/wiki/Packaging:Treatment_Of_Bundled_Libraries#B...
9. https://fedoraproject.org/wiki/Packaging:Guidelines#Macros
10. https://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
--- Fedora Development News ---
The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.
Acceptable Types of Announcements
* Policy or process changes that affect developers.
* Infrastructure changes that affect developers.
* Tools changes that affect developers.
* Schedule changes
* Freeze reminders
Unacceptable Types of Announcements
* Periodic automated reports (violates the INFREQUENT rule)
* Discussion
* Anything else not mentioned above
1. https://admin.fedoraproject.org/mailman/listinfo/devel-announce
---- Your package translation ----
Noriko[1] on Mon Mar 21 23:57:43 UTC 2011 announced[2],
"Dear Fedora package maintainers
Could you all please take a few minutes and check if your packages are on the list[3]and set to allow Fedora Localization Project to translate?
* setuptool: [4]
* pam_krb5: [5]
* pkinit-nss: [6]
* The above packages are on the list but do not allow Fedora Localization teams to upload the translated files. This means that these
packages will not receive any translation from FLP. Please change the setting to allow FLP, or advise us if the maintainers choose having their own translation teams. In that case, the packages may be removed from the list of Fedora Project on tx.net."
1. noriko at fedoraproject.org
2. http://lists.fedoraproject.org/pipermail/devel-announce/2011-March/000769...
3. http://www.transifex.net/projects/p/fedora/r/fedora-15/l/en/
4. http://www.transifex.net/projects/p/setuptool/
5. http://www.transifex.net/projects/p/pam_krb5/
6. http://www.transifex.net/projects/p/pkinit-nss/
---- Fedora Events ----
The purpose of event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning. Events can be added to this page whether or not they have an Ambassador owner. Events without an owner are not eligible for funding, but being listed allows any Ambassador to take ownership of the event and make it eligible for funding. In plain words, Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!
----- Upcoming Events (Dec 2010 - Feb 2011) -----
* North America (NA)[1]
* Central & South America (LATAM): [2]
* Europe, Middle East, and Africa (EMEA)[3]
* India, Asia, Australia (India/APJ)[4]
1. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29
2. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_2
3. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_3
4. http://fedoraproject.org/wiki/Events#FY12_Q1_.28March_2011_-_May_2011.29_4
----- Past Events -----
Archive of Past Fedora Events[1]
1. http://fedoraproject.org/wiki/FedoraEvents/PastEvents
---- Additional information ----
* Reimbursements -- reimbursement guidelines.
* Budget -- budget for the current quarter (as distributed by FAMSCo).
* Sponsorship -- how decisions are made to subsidize travel by community members.
* Organization -- event organization, budget information, and regional responsibility.
* Event reports -- guidelines and suggestions.
* LinuxEvents -- a collection of calendars of Linux events.
-- Marketing --
In this section, we cover the happenings for Fedora Marketing Project for the last week.
http://fedoraproject.org/wiki/Marketing
Contributing Writer: Pascal V. Calarco
We are looking for a new writer to take up the weekly Marketing beat. If you are interested, drop a note to one of the FWN editors!
--- MMM. Almost as tasty as a beefy miracle... your weekly delicious Marketing Meeting Minutes are here! ---
Robyn Bergeron announced[1] the availability of the latest Marketing team minutes
"Greetings, Marketeers!
F15 goodness is well underway. If you're interested in picking up anything on the schedule, including doing a feature profile or want to start digging in on one page release notes, please let us know!
Notes from the meeting are below.
See you next week!
Minutes[2]
Full logs[3]"
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013755.html
2. http://meetbot.fedoraproject.org/fedora-meeting-1/2011-03-22/fedora_marke...
3. http://meetbot.fedoraproject.org/fedora-meeting-1/2011-03-22/fedora_marke...
--- SxSW photobooth awesomeness and its future ---
Clint Savage discussed[1] strategies for making the "SxSW photobooth awesomeness and its future" more universal to FAmNA events.
"As you probably know, I've been hanging around Fedora for a few years now. I helped improve the events that Fedora attends by creating the Fedora EventBox. It's been going really well, but this week, I saw a big improvement because of just a few people at SxSW. I would like to thank Mo, Emily, Spot, Jared and anyone else who helped make the booththere awesome!
. . .
But there's more we can do with this, and that's where I think the value lies. For one, it is cool that each participant get's a nice little card printed right there with a QR code so they can go retrieve it. But it would also be nice to let them share their photos on social networking sites like Facebook, identi.ca, foursquare, twitter, etc. I can also see gaining contributors from this concept, in that they are now 'part' of Fedora's legacy. Maybe having them show up on the FedoraProject front page when an event is happening? I seriously think that this is stuff that everyone in Fedora would love."
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013744.html
-- Fedora In the News --
In this section, we cover news from the trade press and elsewhere that is re-posted to the Fedora Marketing list[1].
http://fedoraproject.org/wiki/Marketing
Contributing Writer: Pascal Calarco
1. http://lists.fedoraproject.org/pipermail/marketing/
--- Tim Burke: Ext4 Is Not Going Anywhere Any Time Soon (muktware.com) ---
Rahul Sundaram forwarded[1] a posting on btrfs and its relation to ext4 in RHEL and Fedora:
"Red Hat engineers work actively to develop these features in the upstream kernel, work both with the Fedora community and others to integrate them for early adopters and then evaluate when they are robust enough for enterprise users."
"File systems are very long lived in the field since users tend to maintain them for years and years. In many cases, enterprise users have external storage so the storage will survive several generations of servers. That means that ext4 is not going anywhere any time soon! That said, Red Hat is an active contributor to the btrfs project and we are actively working on getting some of the key inhibitors for wide btrfs deployment finished with the upstream community"
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013754.html
2. http://www.muktware.com/n/19/2011/846/tim-burke-ext4-not-going-anywhere-a...
--- Linux shakedown: Testing both GNOME 3 and Fedora 15 (ZDNetAsia.com) ---
Rahul Sundaram forwarded[1] a very positive article on both Fedora 15 Alpha and Gnome 3:
"Because this release was so focused on GNOME 3, it was hard to even really notice Fedora 15 in the background. That says a lot about where Fedora is heading. The OS, underlying the desktop, was about as solid an alpha release as I have ever laid fingers on. And running from the live CD was incredible--if someone were to sit at this computer (the very PC I am writing this article on) and begin using the desktop, they would never know they were using a Live CD.
I realize that many of you look down on Fedora for one reason or another. But this testing release should not go unnoticed by the IT public. The GNOME 3 testing release of Fedora 15 is crucial to the growth of both Fedora and GNOME. This release will go a very long way in the testing of what will soon become the default desktop for many Linux distributions (for a very long time). So please, do your fellow Linux community members a favor...test this release and submit bug reports. Your help will be much appreciated and long remembered."
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013753.html
2. http://www.zdnetasia.com/linux-shakedown-testing-both-gnome-3-and-fedora-...
--- Fedora 15 vs Ubuntu Natty Narwhal – The Battle for Your Next Desktop (maketecheasier.com) ---
Rahul Sundaram forwarded[1] another review of Fedora 15 Alpha and the next version of Ubuntu:
"Fedora boasts a pretty “enterprisey” software set. You’re more likely to find a fancy new virtualization program than a 3D shooter here. That’s not to say it’s inappropriate for desktop use, quite the opposite, but expect to find some applications that might not be of much interest to a casual PC user. Still, for those who do like to know, you can expect to find:
* LibreOffice, a “freer” fork of OpenOffice
* BoxGrinder, a virtual appliance utility
* Robotics Suite, a set of tools for robot enthusiasts
* Sugar, a specialized desktop environment for education
* Dynamic Firewall, a way to interactively manage your system firewall
* Gnome 3, of course"
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013752.html
2. http://maketecheasier.com/fedora-15-vs-ubuntu-natty-narwhal-the-battle-fo...
--- Using SELinux and iptables Together (Linux.com) ---
Rahul Sundaram forwarded[1] an article by Red Hat SELinux engineer, Dan Walsh:
"One of the things I have wanted to do with SELinux for years is figure out a way to make SELinux and iptables work together, but each time I looked at it, my use cases became too complicated. James Morris and Paul Moore worked on a tool called Secmark way back in the Red Hat Enterprise Linux (RHEL) 5 time frame. My simple implementation of Secmark is to use iptables rules to define labels on packets as they flow within an SELinux system."
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013751.html
2. http://www.linux.com/learn/tutorials/421152-using-selinux-and-iptables-to...
--- Out with Windows 2000, in with Fedora 14, part 2 (ZDNet UK) ---
Rahul Sundaram forwarded[1] part two of an article from a user who replaces Windows 2000 with Fedora 14 on an older PC:
"Other than these issues, the PC is running great and in fact they immediately noticed a significant speed increase in running their applications. I was surprised that still some tweaks were needed, but when dealing with proprietary hardware/software, we will continue to see these types of problems. My best advice is to direct new users to the Fedora Forums which are very understanding for new users."
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013750.html
2. http://www.zdnet.co.uk/blogs/the-open-source-revolution-10014902/out-with...
--- Speedy 'Wonder Patch' Debuts in New Linux Kernel (PC World) ---
Rahul Sundaram forwarded[1] about the debut of a new patch that increases the linux kernel speed significantly, and which will be available in Fedora 15:
"Back in November I wrote about the 233-line patch that was expected to bring a huge speed boost to version 2.6.38 of the Linux kernel, and that's just what made its widely anticipated debut on Monday night"
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013749.html
2. http://www.pcworld.com/businesscenter/article/222185/speedy_wonder_patch_...
--- Fedora shows off Gnome 3.0 (mybroadband.com South Africa) ---
Rahul Sundaram forwarded[1] some commentary on Gnome 3.0 in Fedora 15:
"The switch to the Gnome 3.0 desktop is the most notable change in this release and one that will no doubt prompt the most discussion. The Gnome 3.0 desktop is a radical departure from the Gnome 2.0"
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013748.html
2. http://mybroadband.co.za/news/software/19021-Fedora-shows-off-Gnome.html
--- Fedora 15 alpha debuts GNOME 3, adds cloud appliance builder (DesktopLinux.com) ---
Rahul Sundaram forwarded[1] another look at Fedora 15 Alpha and Gnome 3:
"The Systemd configuration management technology was available as a technology preview in Fedora 14, but now replaces Upstart and SystemV init as the default initialization system. Systemd is claimed to speed boot-time as well as to provide on-demand loading and unloading of services. Touted Systemd features include system state snapshoting, as well as the ability to track processes, daemons, and sockets.
In the Lovelock alpha, a dozen desktop daemons have been converted to use Systemd service files, while a small number of programs have been patched to take advantage of it, says the Fedora project. Systemd is said to be compatible with legacy SysV init script
For those Fedora users with their heads in the cloud, one of the more interesting additions is BoxGrinder, touted as "an easy to use command line tool to create appliances (virtual images) from simple plaintext application files." BoxGrinder is available for platforms including KVM, Xen, VMware, and EC2, says the project"
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013747.html
2. http://www.desktoplinux.com/news/NS5489739858.html
--- My Wife Loves Gnome 3 (muktware.com) ---
Rahul Sundaram forwarded[1] a non-technical user's experience with Fedora 15 and Gnome 3:
"The most important remark for Gnome 3 came from a non-techie. A user who doesn't much care about kernels and mutters; someone who uses computer to do her job. My wife was sitting right behind me when the machine booted. "Wow...what's that!" I heard someone from behind. I turned and found her looking at my machine. "Is it a new OS? It looks cool!"
I was amazed. As a regular user I was a bit upset with Gnome 3 fearing it will break my usage pattern and here was an ordinary user who was impressed by the new design and approach."
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013746.html
2. http://www.muktware.com/b/14/2011/832/my-wife-loves-gnome-3
--- Playing With Fire, Fedora 15 and Gnome 3 (muktware.com) ---
Rahul Sundaram forwarded[1] another posting from muktware.com on Fedora 15 and Gnome 3 experience:
"I love the design, look and feel of Gnome 3. I am worried about is how is it going to affect my productivity, but I don't want to be too negative before I see the final product. It may just be the status-quo factor bugging me. I don't know. I may end up loving it, the way I love KDE 4!"
The full article is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2011-March/013745.html
2. http://www.muktware.com/a/14/2011/831/playing-fire-fedora-15-and-gnome-3
-- Ambassadors --
This section covers the news surrounding the Fedora Ambassadors Project[1].
Contributing Writer: Sankarshan Mukhopadhyay
1. http://fedoraproject.org/wiki/Ambassadors
--- Welcome New Ambassadors ---
This week the Fedora Ambassadors Project had a couple of new members joining.
Henry from Lithuania mentored by Robert Scheck
Yong Yuan from China mentored by Gerard Braad
--- Summary of traffic on Ambassadors mailing list ---
Gianluca Sforna posted [1] about EuroPython event [2] and enquired if anyone was considering participating.
Igor Pires Soares posted [3] FAmSCo Report for February 2011 [4]
Christoph Wickert posted [5] Meeting Minutes from the EMEA Ambassadors Meeting on 2011-03-09
David Ramsey provided [6] some 'Food for Thought URLs on Fedora 15' or, a set of talking points [7]
Rangeen Basu Roy Chowdhury informed [8] about an upcoming Fedora Electronic Lab talk at the State Level Academician's Convention [9] organized at Bengaluru, India.
Zied Fakhfakh announced [10] the availability of the first Tunisian mirror for Fedora and EPEL [11]
Pierros Papadeas posted [12] Minutes of the FAmSCo meeting [13] for 2011-03-12
Christoph Wickert requested [14] EMEA Ambassadors with swag to update the inventory [15]
María Leandro expressed support and prayers for the people living in Japan [16]. She was joined by others [17]
Francesco Crippa bid [18] for Milan as a venue for FUDCon 2011 [19]. The thread [20] received support
Clint Savage discussed [21] the idea of the 'PhotoBooth' and the future plans around it. Máirín Duffy added [22] some additional notes
Neville A. Cross wrote [23] about marketing and promotional efforts by Microsoft at Nicaragua involving funding events on condition of talking about/demonstrating inter-operability. Fedora Ambassadors contributed from their experience [24] in similar situations and provided guidance about how to deal with situations arising out of such partnership requests.
Bertrand Juglas informed [25] about the acceptance of the virtualization workshop at LOAD
Buddhika Kurera informed [26] about Fedora Project being accepted at the GSoC2011.
Igor Pires Soares posted [27] Minutes of Meeting from FAmSCo meeting of 2011-03-19 [28]
Adam Miller informed [29] about the plans for the Texas Linux Fest 2011 [30]
1. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017150.html
2. http://ep2011.europython.eu/
3. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017154.html
4. https://fedoraproject.org/wiki/FAmSCo_report_2011-02
5. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017157.html
6. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017162.html
7. https://fedoraproject.org/wiki/Fedora_15_talking_points
8. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017164.html
9. http://www.fsmk.org/node/66
10. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017166.html
11. http://mirrors.fedoraproject.org/publiclist
12. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017179.html
13. http://meetbot.fedoraproject.org/fedora-meeting/2011-03-12/famsco.2011-03...
14. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017181.html
15. https://fedorahosted.org/emea-swag-tracking/wiki/Inventory
16. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017185.html
17. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/thread.ht...
18. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017193.html
19. https://fedoraproject.org/wiki/FUDCon:Bid_for_Milan_2011
20. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/thread.ht...
21. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017204.html
22. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017205.html
23. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017212.html
24. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/thread.ht...
25. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017224.html
26. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017230.html
27. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017231.html
28. http://meetbot.fedoraproject.org/fedora-meeting/2011-03-19/famsco.2011-03...
29. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017235.html
30. https://fedoraproject.org/wiki/Texas:LinuxFest_2011
--- Summary of events reported on Ambassadors mailing list ---
Nilesh Vaghela reported [1] on a Open Source/Linux seminar organized at the SAL Engineering College, Ahmedabad, Gujarat
Heherson Pagcaliwagan reported [2] on the SGC2011 event [3]
1. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017152.html
2. http://lists.fedoraproject.org/pipermail/ambassadors/2011-March/017178.html
3. http://testmsg.wordpress.com/2011/03/12/sgc-2011-event-report/
--- Summary of traffic on FAmSCo mailing list ---
Caius Chance posted [1] about specious fraudulent transactions in reimbursement in the Bangladesh Community. Max Spevack suggested [2] that all sides of the story need to be heard and listened to before an accusation of impropriety. Pierros Papadeas pointed out [3] that this specific thread was "officially halted" until the issue is resolved and addditionally informed that FAmSCo would have a private meeting with all parties.
Max Spevack provided an update [4] about the Budget [5]
Pierros Papadeas proposed [6] re-organizing tasks upon which Rahul Sundaram was working. Gerard Braad suggested [7] about the need to inform FAmSCo about an upcoming busy period so as to coordinate involvement in tasks.
Max Spevack proposed [8] two topics for the EMEA Ambassadors meeting and assigned their ownership to Pierros Papadeas
Neville A. Cross asked [9] about the time for the FAmSCo meeting in conjunction with the time changes associated with DST. The thread [10] includes discussions around a time that is good for FAmSCo members to attend. And further discussions around meeting time occurred on a different thread [11]
Larry Cafiero asked about [12] a possible mistake in months (March in place of April) in the meeting minutes and received confirmation that it was indeed a mistake and the intended month is April.
1. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000697.html
2. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000699.html
3. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000702.html
4. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000698.html
5. https://fedoraproject.org/wiki/Community_Architecture_expenses
6. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000704.html
7. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000707.html
8. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000711.html
9. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000712.html
10. http://lists.fedoraproject.org/pipermail/famsco/2011-March/thread.html#712
11. http://lists.fedoraproject.org/pipermail/famsco/2011-March/thread.html#721
12. http://lists.fedoraproject.org/pipermail/famsco/2011-March/000722.html
-- QualityAssurance --
In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].
Contributing Writer: Adam Williamson
1. http://fedoraproject.org/wiki/QA
2. http://fedoraproject.org/wiki/QA/Join
--- Test Days ---
Thursday 2011-03-17 was preupgrade Test Day[1]. A good group of testers showed up, but testing was somewhat complicated by underlying bugs in anaconda. However, the testers were able to check that most of preupgrade itself was working as intended. Rui He posted a recap to the list[2].
This Thursday, 2011-03-24, is power management Test Day[3], where we'll be testing how well various common power management operations work on a range of systems. The main focus of this event is to check common power management features on a wide range of hardware, so we really need as many people as possible to come along. Please come out if you have a bit of spare time.
Next Tuesday (note the special day!), 2011-03-29, will be printing Test Day[4]. We'll be aiming to test out Fedora 15's printing stack with as many different printers as possible, so if you have a printer and a pulse, please come and join us!
Next Thursday, 2011-03-31, will be ABRT Test Day[5]. As well as checking that ABRT (Fedora's automated crash report tool) is working as expected for Fedora 15, we'll be testing out a big new feature, the retrace server[6]. This allows you to submit crash reports to a remote server which will generate the backtrace - avoiding the need for you to download and install often large debuginfo packages in order to submit reports. Please come along and help us test this exciting new feature!
1. http://fedoraproject.org/wiki/Test_Day:2011-03-17_Preupgrade
2. http://lists.fedoraproject.org/pipermail/test/2011-March/097977.html
3. http://fedoraproject.org/wiki/Test_Day:2011-03-24
4. http://fedoraproject.org/wiki/Test_Day:2011-03-29
5. http://fedoraproject.org/wiki/Test_Day:2011-03-31_ABRT_Retrace_Server
6. http://fedoraproject.org/wiki/Features/RetraceServer
--- Release criteria revisions ---
Adam Williamson proposed several alterations to the release criteria[1], covering several issues that had become clear at recent blocker meetings. The alterations attempted to account for bugs that were specific to particular keymaps or languages, cover firstboot, cover unintended installations, and clarify a few other points. Andre Robatino proposed an additional criterion requiring a working media check process in the installer[2], an idea Adam supported[3]. James Laska recommended caution to avoid tying the criterion too closely to a specific implementation[4].
1. http://lists.fedoraproject.org/pipermail/test/2011-March/097859.html
2. http://lists.fedoraproject.org/pipermail/test/2011-March/097861.html
3. http://lists.fedoraproject.org/pipermail/test/2011-March/097863.html
4. http://lists.fedoraproject.org/pipermail/test/2011-March/097870.html
--- Nightly builds via Koji ---
In response to a query from Gregory Woodbury about nightly builds being stalled[1], Kevin Fenzi explained[2] that this was due to a problem on the compose machine. He went on to announce that the nightly builds would soon be done via Koji, which will result in the builds happening much faster, guarantee that they are built in exactly the same way as official composes, and allow for an archive of recent nightly builds to be kept, making regression testing easier.
1. http://lists.fedoraproject.org/pipermail/test/2011-March/097856.html
2. http://lists.fedoraproject.org/pipermail/test/2011-March/097860.html
--QA group governance
Jóhann Guðmundsson raised some questions regarding the governance of the QA group[1], including the idea of an elected board to handle some decision making when representing the group as a whole. Stephen Smoogen noted that SIGs do not generally have formal voting structures[2], while leaving open the question of whether QA is (or should be) a SIG or a Steering Committee. Clyde E. Kunkel noted that the functions of the QA team are mostly advisory rather than decision-making, and expressed a desire for an organization chart (or 'wiring diagram') for the various groups that make up the Fedora project[3]. Adam Williamson pointed out that the Board had worked on such a diagram at FUDCon Tempe, and a copy of the image may be available[4]. He replied to Jóhann's question about the status of Red Hat employees in the group by saying they tried not to see their position as giving them automatic decision-making power on behalf of the group, but admitted that in practice, other groups often seem to come directly to the Red Hat employees in the group and consider their responses as representing the QA group as a whole.
1. http://lists.fedoraproject.org/pipermail/test/2011-March/097891.html
2. http://lists.fedoraproject.org/pipermail/test/2011-March/097899.html
3. http://lists.fedoraproject.org/pipermail/test/2011-March/097902.html
4. http://lists.fedoraproject.org/pipermail/test/2011-March/097910.html
--- Fedora 15 Beta preparation ---
The second Beta blocker/nice-to-have review meeting took place on 2011-03-18[1], and the team worked through the full list of proposed Beta blocker and nice-to-have bugs. The first automated Beta acceptance test run was scheduled for 2011-03-17, but this was not possible due to underlying issues in anaconda at the time, as discussed at the weekly meeting of 2011-03-21[2]. At the same meeting, James Laska noted that the Beta test compose was at risk due to the same problems, and committed to providing updated images to test candidate fixes for the problems.
1. http://meetbot.fedoraproject.org/fedora-bugzappers/2011-03-18/f-15-beta-b...
2. http://fedoraproject.org/wiki/QA/Meetings/20110321
-- Security Advisories --
In this section, we cover Security Advisories from fedora-package-announce from the past week.
http://lists.fedoraproject.org/pipermail/package-announce
Contributing Writer: Pascal Calarco
--- Fedora 15 Security Advisories ---
* php-pear-1.9.2-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0564...
* krb5-1.9-6.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0564...
* wordpress-3.1-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0564...
* mailman-2.1.14-5.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0563...
* mhonarc-2.6.18-3.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0563...
* pidgin-2.7.11-1.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0563...
* libvirt-0.8.8-3.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0562...
* gnash-0.8.9-0.1.20110312git.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0561...
* ember-0.6.0-5.fc15 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0560...
--- Fedora 14 Security Advisories ---
* perl-Gtk2-MozEmbed-0.08-6.fc14.25 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* mozvoikko-1.0-20.fc14.1 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* gnome-web-photo-0.9-19.fc14.1 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* galeon-2.0.7-39.fc14.1 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* gnome-python2-extras-2.25.3-29.fc14.1 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* xulrunner-1.9.2.16-1.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* firefox-3.6.16-1.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* mhonarc-2.6.18-3.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* postfix-2.7.3-1.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* mailman-2.1.13-7.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0563...
* samba-3.5.8-74.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0562...
* policycoreutils-2.0.85-19.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0562...
* subversion-1.6.16-1.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0560...
* seamonkey-2.0.12-1.fc14 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0560...
--- Fedora 13 Security Advisories ---
* postfix-2.7.3-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* perl-Gtk2-MozEmbed-0.08-6.fc13.23 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* mozvoikko-1.0-20.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* gnome-web-photo-0.9-18.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* galeon-2.0.7-39.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* gnome-python2-extras-2.25.3-28.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* xulrunner-1.9.2.16-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* firefox-3.6.16-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* mhonarc-2.6.18-3.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0565...
* mailman-2.1.12-17.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0563...
* pidgin-2.7.11-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0562...
* samba-3.5.8-74.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0562...
* openssl-1.0.0d-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0561...
* subversion-1.6.16-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0560...
* seamonkey-2.0.12-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2011-March/0560...
-- LATAM Fedora! --
LATAM Fedora is a regular column of Spanish language contributions around open source software. It is our first expansion into incorporating foreign language content into FWN.
This week's contribution is from Guillermo Gómez, a primer on the SOX audio manipulation package. Enjoy!
--- SOX ---
SoX[1], la navaja suiza para la manipulación de audio.
---- Agregando Soporte mp3 y m4a ----
Fedora no incluye soporte para MP3 en sus paquetes multimedia, debido a problemas de patentes sobre el algoritmo que permite comprimir y descromprimir mp3. De forma similar ocurre con el formato m4a. Sin embargo usted puede vivir en ciertos países donde no apliquen las limitaciones de la legislación de los EEUU, entonces si es así, veamos cómo podemos agregar el soporte deseado para mp3 y m4a entre otros formatos a sox.
---- Agregar soporte recompilando el Source RPM (SRPM) ----
----- Requisitos -----
* Herramientas para compilación
* rpmbuild
* yum-buildep
* De RPM Fusion, lame, lame-libs, lame-devel, libmad, libmad-devel, ffmpeg y ffmpeg-devel
El procedimiento de instalación de software es, como root:
Herramientas para compilar
$ yum -y groupinstall "Development Tools"
$ yum -y install rpmdevtools
Dependencias para poder compilar sox según Fedora
$ yum-builddep -y sox
Librerías adicionales para la compilación (soporte mp3)
$ yum -y install lame lame-libs lame-devel
$ yum -y install libmad libmad-devel
$ yum -y install ffmpeg ffmpeg-devel
---- Construcción e Instalación del RPM ----
Ahora para reconstruir SoX con soporte mp3 el procedimiento como usuario regular es:
$ cd
$ rpmdev-setuptree (si no lo ha hecho antes)
$ yumdownloader --source sox (descarga los fuentes srpm)
$ rpmbuild --rebuild sox-14.3.0-1.fc13.src.rpm (compila/construye rpm)
$ cd rpmbuild/RPMS/x86_64
$ su
*contraseña*
# rpm -vhi --force sox-14.3.0-1.fc13.x86_64.rpm
Preparando... ########################################### [100%]
1:sox ########################################### [100%]
...
# sox -h
...
AUDIO FILE FORMATS: 8svx aif aifc aiff aiffc al amb au avi avr caf cdda cdr cvs cvsd cvu dat dvms f32 f4 f64 f8 fap ffmpeg flac fssd gsm hcom htk ima ircam la lpc lpc10 lu m4a mat mat4 mat5 maud mp2 mp3 mp4 mpg nist ogg paf prc pvf raw s1 s16 s2 s24 s3 s32 s4 s8 sb sd2 sds sf sl smp snd sndfile sndr sndt sou sox sph sw txw u1 u16 u2 u24 u3 u32 u4 u8 ub ul uw vms voc vorbis vox w64 wav wavpcm wmv wv wve xa xi
PLAYLIST FORMATS: m3u pls
...
NOTA: Procedimiento probado en F8, F9, F10, F11, F12 y F13, en el tiempo las versiones pueden cambiar, en el ejemplo se muestra la versión más reciente. Para versiones anteriores a F13, el compilado es para i586, a partir de F12 es i686. En el caso de x86_64, el compilado está en el directorio rpmbuild/RPMS/x86_64 .
Note la inclusión de mp3 y m4a en los formatos soportados. Ahora puede reproducir su mp3 o m4a desde la consola. Sox también permite convertir entre formatos y tiene muchas otras aplicaciones. Abajo reproduzco un mp3 de AC/DC.
---- Convertir mp3 ----
Otra aplicación común de sox es convertir de un formato a otro, por ejemplo de mp3 a cdr o wav, con cdr se está listo para quemar un CD Audio :)
$ sox -V Boinga.mp3 Boinga.cdr
sox: Detected file format type: mp3
sox: Input file Boinga.mp3: using sample rate 44100
size shorts, encoding MPEG audio (layer I, II or III), 2 channels
sox: Output file Boinga.cdr: using sample rate 44100
size shorts, encoding signed (2's complement), 2 channels
sox: Output file: comment "Processed by SoX"
Convirtamos ahora a un formato libre, ogg.
$ sox -V Boinga.mp3 Boinga.ogg
sox: Detected file format type: mp3
sox: Input file Boinga.mp3: using sample rate 44100
size shorts, encoding MPEG audio (layer I, II or III), 2 channels
sox: Output file Boinga.ogg: using sample rate 44100
size shorts, encoding Vorbis, 2 channels
sox: Output file: comment "Processed by SoX"
Veamos los tamaños resultantes solo por curiosidad incluyendo otros formatos sin ningún parámetro adicional al convertir, es decir, usando los valores por omisión.
$ ls -lh Boinga*
-rw-rw-r-- 1 gomix gomix 23M Sep 22 14:50 Boinga.au
-rw-rw-r-- 1 gomix gomix 23M Sep 22 14:51 Boinga.avr
-rw-rw-r-- 1 gomix gomix 23M Sep 22 14:24 Boinga.cdr
-rw-rw-r-- 1 gomix gomix 2.6M Nov 11 2006 Boinga.mp3
-rw-rw-r-- 1 gomix gomix 1.5M Sep 22 14:26 Boinga.ogg
-rw-rw-r-- 1 gomix gomix 23M Sep 22 14:35 Boinga.wav
AplicacionesDeUsuario_Audio_Sox_mp3_sox-play-mp3.png (25.2 kB)
Guillermo Gómez
- end FWN 268 -
13 years, 2 months
QA coming, probably
by Adam Williamson
I'm aiming to get a QA beat in later today, I'm juggling quite a lot of
balls though so it may be a few hours. sorry!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 3 months