[fedora-electronic-lab] What if I want to maintain ALL my packages on EPEL as from now on ?
by Chitlesh GOORAH
Hello there,
It's been a while since I'm considering my commitment towards the FEL,
since Fedora (this distribution) 's 6months development cycle is
becoming a headache for me release after release.
I simply don't have time to fix issues related with compiler updates.
As a hardware engineer, this is not how I wish to spend my leisure
time. More than 90% of my FEL development time was about compiler
fixes than something related to its features. My current Fedora
packages are mostly for the microelectronics engineering, which
requires
* a stable and long term support platform for the user
* and less distraction for me (less software update compatibility
nuisance) so that I have time to improve theses opensource EDA
software by actually porting Semiconductor Physics to software.
So here I am in front of the EPEL community, can I _only_ maintain my
>50 mature packages for EPEL only (and no support for Fedora anymore)
* which was developed more than 5 years ago and being currently used
in the industry
* which require few minor updates per year
* which some of them are already within the EPEL repositories
* which are in the fedora repositories for more than 3 years (for more
than 5 fedora releases) and being used by many small companies and
universities around the world.
------------ FROM http://fedoraproject.org/wiki/EPEL/FAQ#Contributing_to_EPEL
Is it possible to get a package only into EPEL and not Fedora?
Simply go through the review process for Fedora and specify only EL
targets for the initial import. But note that maintaining packages in
Fedora has many advantages for you, you should consider maintaining
the package in both Fedora and EPEL.
------------------------------
However since I simply don't have the time to spend on politics and a
tight release cycle, my only options so that I can still improve the
existing EDA tools myself (as upstream) would be:
1* provide EPEL support only and no support on Fedora or
2* stop maintaining all my fedora packages and wait till someone cares
to take over
Can a packager like me opt only option 1 ?
If option 1 is possible for me, then if by the end of August noone
wants to maintain my packages for fedora 12 and onwards, I would mark
them all as dead packages and concentrate only for their respective
EPEL branches.
Cheers,
Chitlesh Goorah
13 years, 9 months
[fedora-electronic-lab] Introducing myself
by Dheeraj Kumar
Hello all,
I am Dheeraj Kumar, an Embedded professional with around 3 years of
experience in Embedded Systems, linux Device drivers, BSP, arm tool chain
and Hardware debugging. Currently i am working with Stryker, INDIA. prior to
that i worked with C-DAC Chennai, they are into FOSS and have a product name
BOSS. there i was involved in porting OS on different platforms. and
microcontroller programming with tiny OS and nes C. i have also worked on
open source hardware like Arduino, freeduino and beagle board etc.
If there is any work related to my field, please let me know.
Best Regards
--
Dheeraj Kumar
http://www.linkedin.com/in/dhiry2k
09871019901
13 years, 9 months
[fedora-electronic-lab] [dev-notice] perl-Verilog-Perl 3.250 was built but needs push to mirrors
by Chitlesh GOORAH
Hello there,
NOTICE to FEL maintainers:
perl-Verilog-Perl was built for all supported Fedora and EPEL CVS
branches, but haven't yet been pushed to Fedora YUM repositories.
Package required to push to mirrors: perl-Verilog-Perl
Version : 3.250
Branches which already received the updates: EL-5, EL-6, rawhide
Branches required to push to mirrors : F-12, F-13
How to push to Fedora repositories:
- Pull the rpm from koji
- Test them
- then use bodhi to push to their respective repos on
https://admin.fedoraproject.org/updates.
Other comments: During the build, the package passed all the self-checks.
- Upstream release notes:
* Verilog::Language 3.250 2010/06/21
** Add parsing of "defparam", including SigParser::defparam callback,
Netlist::ContAssign object, and accessors. [Pierre-David Pfister]
**** Fix complex {...} port declarations, bug262. [Evgeni Stavinov]
--------------
regards,
Chitlesh
13 years, 10 months
