From gdk at redhat.com Tue Jun 3 14:16:23 2008 From: gdk at redhat.com (Greg Dekoenigsberg) Date: Tue, 3 Jun 2008 10:16:23 -0400 (EDT) Subject: Hello? Message-ID: Hi all. Just want to post to the list to see who's about. Holla back! :) --g From jvenable at redhat.com Tue Jun 3 14:20:39 2008 From: jvenable at redhat.com (Jennifer Venable) Date: Tue, 03 Jun 2008 10:20:39 -0400 Subject: Hello? In-Reply-To: References: Message-ID: <48455337.50006@redhat.com> I'm here. Greg Dekoenigsberg wrote: > > Hi all. Just want to post to the list to see who's about. Holla > back! :) > > --g > > _______________________________________________ > Fedora-isv-sig-list mailing list > Fedora-isv-sig-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list -- ?Jennifer Venable Red Hat, Inc. 1801 Varsity Drive Raleigh, NC 27606 phone: 919-754-4096 fax: 919-754-3729 email: jvenable at redhat.com From chris at zenoss.com Tue Jun 3 14:23:07 2008 From: chris at zenoss.com (Christopher Blunck) Date: Tue, 3 Jun 2008 10:23:07 -0400 Subject: Hello? In-Reply-To: <48455337.50006@redhat.com> References: <48455337.50006@redhat.com> Message-ID: I'm also on the list as well. Just joined this morning. Looking to get some help in getting Zenoss into some official repository.... -c On Jun 3, 2008, at 10:20 AM, Jennifer Venable wrote: > I'm here. > Greg Dekoenigsberg wrote: >> >> Hi all. Just want to post to the list to see who's about. Holla >> back! :) >> >> --g >> >> _______________________________________________ >> Fedora-isv-sig-list mailing list >> Fedora-isv-sig-list at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list > > -- > Jennifer Venable > Red Hat, Inc. > 1801 Varsity Drive > Raleigh, NC 27606 > phone: 919-754-4096 > fax: 919-754-3729 > email: jvenable at redhat.com > > _______________________________________________ > Fedora-isv-sig-list mailing list > Fedora-isv-sig-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list From gdk at redhat.com Tue Jun 3 14:59:02 2008 From: gdk at redhat.com (Greg Dekoenigsberg) Date: Tue, 3 Jun 2008 10:59:02 -0400 (EDT) Subject: Hello? In-Reply-To: References: <48455337.50006@redhat.com> Message-ID: On Tue, 3 Jun 2008, Christopher Blunck wrote: > I'm also on the list as well. Just joined this morning. Looking to get > some help in getting Zenoss into some official repository.... Well, that's just the kind of thing I like to hear! Are you planning on going to the Red Hat Summit? --g From chris at zenoss.com Tue Jun 3 15:01:31 2008 From: chris at zenoss.com (Christopher Blunck) Date: Tue, 3 Jun 2008 11:01:31 -0400 Subject: Hello? In-Reply-To: References: <48455337.50006@redhat.com> Message-ID: <45DDCBCF-10EF-43FB-83B6-A873CCB65500@zenoss.com> Nope - not in the budget.... -c On Jun 3, 2008, at 10:59 AM, Greg Dekoenigsberg wrote: > > > On Tue, 3 Jun 2008, Christopher Blunck wrote: > >> I'm also on the list as well. Just joined this morning. Looking >> to get some help in getting Zenoss into some official repository.... > > Well, that's just the kind of thing I like to hear! Are you > planning on going to the Red Hat Summit? > > --g > From jvenable at redhat.com Tue Jun 3 15:07:50 2008 From: jvenable at redhat.com (Jennifer Venable) Date: Tue, 03 Jun 2008 11:07:50 -0400 Subject: Hello? In-Reply-To: <45DDCBCF-10EF-43FB-83B6-A873CCB65500@zenoss.com> References: <48455337.50006@redhat.com> <45DDCBCF-10EF-43FB-83B6-A873CCB65500@zenoss.com> Message-ID: <48455E46.6000103@redhat.com> Zenoss is a sponsor of the Summit -- I'm not sure what comes with a sponsorship, but maybe you can check with your marketing folks to see if that's an angle to help you get there ... Christopher Blunck wrote: > Nope - not in the budget.... > > > -c > > On Jun 3, 2008, at 10:59 AM, Greg Dekoenigsberg wrote: > >> >> >> On Tue, 3 Jun 2008, Christopher Blunck wrote: >> >>> I'm also on the list as well. Just joined this morning. Looking to >>> get some help in getting Zenoss into some official repository.... >> >> Well, that's just the kind of thing I like to hear! Are you planning >> on going to the Red Hat Summit? >> >> --g >> > -- ?Jennifer Venable Red Hat, Inc. 1801 Varsity Drive Raleigh, NC 27606 phone: 919-754-4096 fax: 919-754-3729 email: jvenable at redhat.com From chris at zenoss.com Tue Jun 3 15:11:50 2008 From: chris at zenoss.com (Christopher Blunck) Date: Tue, 3 Jun 2008 11:11:50 -0400 Subject: Hello? In-Reply-To: <48455E46.6000103@redhat.com> References: <48455337.50006@redhat.com> <45DDCBCF-10EF-43FB-83B6-A873CCB65500@zenoss.com> <48455E46.6000103@redhat.com> Message-ID: <034F4CC3-B473-4D8C-828A-B2BA17EE677D@zenoss.com> Don't think it's a money budget. Think the problem is a time budget. ;-) -c On Jun 3, 2008, at 11:07 AM, Jennifer Venable wrote: > Zenoss is a sponsor of the Summit -- I'm not sure what comes with a > sponsorship, but maybe you can check with your marketing folks to > see if that's an angle to help you get there ... > > Christopher Blunck wrote: >> Nope - not in the budget.... >> >> >> -c >> >> On Jun 3, 2008, at 10:59 AM, Greg Dekoenigsberg wrote: >> >>> >>> >>> On Tue, 3 Jun 2008, Christopher Blunck wrote: >>> >>>> I'm also on the list as well. Just joined this morning. Looking >>>> to get some help in getting Zenoss into some official >>>> repository.... >>> >>> Well, that's just the kind of thing I like to hear! Are you >>> planning on going to the Red Hat Summit? >>> >>> --g >>> >> > > -- > Jennifer Venable > Red Hat, Inc. > 1801 Varsity Drive > Raleigh, NC 27606 > phone: 919-754-4096 > fax: 919-754-3729 > email: jvenable at redhat.com > From kwade at redhat.com Tue Jun 3 15:54:33 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Tue, 03 Jun 2008 08:54:33 -0700 Subject: Hello? In-Reply-To: References: <48455337.50006@redhat.com> Message-ID: <1212508473.8355.165.camel@calliope.phig.org> On Tue, 2008-06-03 at 10:23 -0400, Christopher Blunck wrote: > I'm also on the list as well. Just joined this morning. Looking to > get some help in getting Zenoss into some official repository.... Thanks for joining. I think the last post about Zenoss packaging I saw was this one: https://www.redhat.com/archives/epel-devel-list/2008-February/msg00147.html Can you let us know how it has gone since then? Are there additional Fedora barriers you've run into or been stuck behind? Since one goal here is to help each other work through internal issues, if there is anything you can address about challenges with the sponsoring corporation ... feel free to lay it bare. (Keep in mind we are publicly archived.) - Karsten -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From gdk at redhat.com Fri Jun 6 20:47:56 2008 From: gdk at redhat.com (Greg Dekoenigsberg) Date: Fri, 6 Jun 2008 16:47:56 -0400 (EDT) Subject: ISV guide to the Summit Message-ID: To all of our partner friends: We've received a lot of inquiries from our partners about packaging their software in RPM format for use with Fedora. With good reasons: * Millions of Fedora users can install any RPM in the Fedora universe with one simple command. * RPM is the cornerstone of Linux systems management applications, allowing sysadmins to manage a complete list of all software on their systems, through many different tools. * RPM is also the basis of much of the appliance work that Red Hat is advancing. Putting your software into RPM format makes it much simpler to build Live CDs, network install images, or even virtual appliances around your software solution. Any open source software provider can package their work as an RPM for Fedora. Getting software into Fedora is not as easy as it could be, but it's not that difficult, either -- and we are committed to working with our partners to make it as painless as possible. At the Red Hat Summit / Fedora User and Developer conference, developers have unprecedented access to the knowledge of the Red Hat and Fedora communities. For those who are interested specifically in learning how to make the best use of RPM and Fedora, we would like to recommend the following sessions: * Topic: Fedora images and live CDs. Presenter: Jeremy Katz Time: Wednesday 6/18, 11:30am - 12:30pm Location: Red Hat Summit Session Hall * Topic: How to make good RPM packages Presenter: Tom Callaway Time: Wednesday 6/18, 1:30pm - 2:30pm Location: Red Hat Summit Session Hall * Topic: Building Appliances with the Red Hat Appliance OS Presenter: Bryan Kearney Time: Wednesday 6/18, 2:45pm - 3:45pm Location: Red Hat Summit Session Hall * Topic: Fedora packages for RHEL Presenter: Karsten Wade Time: Thursday 6/19, 2:45pm - 3:45pm Location: Red Hat Summit Session Hall * Topic: ISV Packaging Hackfest Presenter: Various Time: Thursday 6/19, 10am - 4pm Location: Fedora Hackfest Area * Topic: Java Packaging Hackfest Presenter: Various Time: Friday 6/20, 10am - 4pm Location: Fedora Hackfest Area Also, on Saturday 6/21, we will be holding the Fedora Users and Developers Conference at Boston University, just minutes from the Hynes Convention Center. FUDCons are the lifeblood of the Fedora community; every FUDCon draws the best and the brightest of the Fedora community from all over the world. We urge Summit participants who are interested in learning more about Fedora to attend this exceptional conference. Learn more about FUDCon at: http://fedoraproject.org/wiki/FUDCon/FUDConF10 If you have any questions, please contact Greg DeKoenigsberg , Paul Frields or Max Spevack for more information. We look forward to seeing you at the Summit, and at FUDCon. --g From kwade at redhat.com Thu Jun 12 15:08:37 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Thu, 12 Jun 2008 08:08:37 -0700 Subject: what do you want to know about EPEL? Message-ID: <1213283317.3866.234.camel@calliope.phig.org> I'm doing the final work on my presentation on EPEL[1] at the Red Hat Summit, and I'm wondering if there any questions you all have I should address? Generally, the approach is to describe what EPEL is (and what it isn't), and the various reasons why it is an important enough goal to warrant doing whatever it takes to get software in to RPM. Also, I'm going to touch upon some of the new work we are doing to enable ISVs to be successful -- this SIG, the other sessions at the Summit and FUDCon, etc. Let me know if there is anything you'd want to hear more of, less of, etc. thx - Karsten [1] https://fedoraproject.org/wiki/EPEL -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From lee.faus at alfresco.com Thu Jun 12 15:18:56 2008 From: lee.faus at alfresco.com (Lee Faus) Date: Thu, 12 Jun 2008 16:18:56 +0100 (BST) Subject: what do you want to know about EPEL? In-Reply-To: <1213283317.3866.234.camel@calliope.phig.org> Message-ID: <4493757.1621213283936872.JavaMail.lfaus@lee-imac.local> When is you talk? 1) How do appliances fit into EPEL? 2) Is RPM a requirement for EPEL? 3) If we deploy to EPEL, do all of the packages we depend on need to be in EPEL as well? 3a) If so, who is responsible for getting those packages into EPEL? 4) How is Fedora/Community prepared to help getting business applications into EPEL? 4a) Are there FTEs devoted to getting business applications into EPEL? 5) Do you need to go through Fedora to get to EPEL? Lee ----- Original Message ----- From: "Karsten 'quaid' Wade" To: fedora-isv-sig-list at redhat.com Sent: Thursday, June 12, 2008 11:08:37 AM GMT -05:00 US/Canada Eastern Subject: what do you want to know about EPEL? I'm doing the final work on my presentation on EPEL[1] at the Red Hat Summit, and I'm wondering if there any questions you all have I should address? Generally, the approach is to describe what EPEL is (and what it isn't), and the various reasons why it is an important enough goal to warrant doing whatever it takes to get software in to RPM. Also, I'm going to touch upon some of the new work we are doing to enable ISVs to be successful -- this SIG, the other sessions at the Summit and FUDCon, etc. Let me know if there is anything you'd want to hear more of, less of, etc. thx - Karsten [1] https://fedoraproject.org/wiki/EPEL -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 _______________________________________________ Fedora-isv-sig-list mailing list Fedora-isv-sig-list at redhat.com https://www.redhat.com/mailman/listinfo/fedora-isv-sig-list From bkearney at redhat.com Thu Jun 12 15:26:59 2008 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 12 Jun 2008 11:26:59 -0400 Subject: what do you want to know about EPEL? In-Reply-To: <4493757.1621213283936872.JavaMail.lfaus@lee-imac.local> References: <4493757.1621213283936872.JavaMail.lfaus@lee-imac.local> Message-ID: <48514043.3000502@redhat.com> Summarizing what Lee Said.... Walk them through how they could get into EPEL, showing people from Fedora, Red Hat, the community as a whole, and ISV. Reading into what Lee said.. I see a possible assumption embedded in (3a and 4a) that it is not the ISV. Is this true, or not. Also.. explain how changes submitted to the EPEL code may or may not make it back upstream. I think there is a misunderstanging between what code is unique to EPEL, and what is pulled from upstream. Building on above, perhaps you walk them through initial inclusion and first bug. I would also address the common stumbling blocks, and how to work around them. --bk Lee Faus wrote: > When is you talk? > > 1) How do appliances fit into EPEL? > 2) Is RPM a requirement for EPEL? > 3) If we deploy to EPEL, do all of the packages we depend on need to be in EPEL as well? > 3a) If so, who is responsible for getting those packages into EPEL? > 4) How is Fedora/Community prepared to help getting business applications into EPEL? > 4a) Are there FTEs devoted to getting business applications into EPEL? > 5) Do you need to go through Fedora to get to EPEL? > > Lee > ----- Original Message ----- > From: "Karsten 'quaid' Wade" > To: fedora-isv-sig-list at redhat.com > Sent: Thursday, June 12, 2008 11:08:37 AM GMT -05:00 US/Canada Eastern > Subject: what do you want to know about EPEL? > > I'm doing the final work on my presentation on EPEL[1] at the Red Hat > Summit, and I'm wondering if there any questions you all have I should > address? > > Generally, the approach is to describe what EPEL is (and what it isn't), > and the various reasons why it is an important enough goal to warrant > doing whatever it takes to get software in to RPM. > > Also, I'm going to touch upon some of the new work we are doing to > enable ISVs to be successful -- this SIG, the other sessions at the > Summit and FUDCon, etc. > > Let me know if there is anything you'd want to hear more of, less of, > etc. > > thx - Karsten > [1] https://fedoraproject.org/wiki/EPEL From tcallawa at redhat.com Thu Jun 12 15:29:46 2008 From: tcallawa at redhat.com (Tom "spot" Callaway) Date: Thu, 12 Jun 2008 11:29:46 -0400 Subject: what do you want to know about EPEL? In-Reply-To: <4493757.1621213283936872.JavaMail.lfaus@lee-imac.local> References: <4493757.1621213283936872.JavaMail.lfaus@lee-imac.local> Message-ID: <1213284586.3461.160.camel@localhost.localdomain> I'll take a shot at this. Note that I don't speak for the EPEL Steering Committee. :) On Thu, 2008-06-12 at 16:18 +0100, Lee Faus wrote: > 1) How do appliances fit into EPEL? I'm not sure this is relevant. EPEL is a repository of RPM packages built against RHEL 4 and 5. If your appliance can make use of those RPM packages, then it would seem that EPEL is a good fit for that appliance. > 2) Is RPM a requirement for EPEL? Yes. > 3) If we deploy to EPEL, do all of the packages we depend on need to > be in EPEL as well? Yes. > 3a) If so, who is responsible for getting those packages into EPEL? Someone? Anyone? There is no requirement that anyone in particular do it, but they do need to be there. You can't put the cart before the horse, but we don't care who maintains the horse (as long as someone does). :) > 4) How is Fedora/Community prepared to help getting business > applications into EPEL? This is a good question. I suspect that individuals who are interested in these applications will be motivated to help. Some of the rest of us are just interested in helping FOSS companies get more exposure and are volunteering our time and resources to assist. We won't really have a good idea until we get the ball rolling forward. > 4a) Are there FTEs devoted to getting business applications into EPEL? I'm not tasked for this as my only role as a FTE for Red Hat, but as the Fedora Engineering Manager, I'm volunteering quite a bit of my time to assist with this process. So, you've got at least 1/4 of 1. ;) > 5) Do you need to go through Fedora to get to EPEL? So, the answer here is "sortof". EPEL uses the Fedora Packaging Guidelines, so if your package meets the criteria for acceptance in Fedora, it is also ok for EPEL. The maintainer will also need to agree to the Fedora CLA (or negotiate a separate corporate contributor agreement) and have a Fedora account, in order to maintain the packages. However: If you really don't want your package in Fedora, just EPEL, we can do that. I hope that helps, ~spot From smooge at gmail.com Fri Jun 13 22:22:47 2008 From: smooge at gmail.com (Stephen John Smoogen) Date: Fri, 13 Jun 2008 16:22:47 -0600 Subject: Late to the party... Message-ID: <80d7e4090806131522i7ac1bbc0tcf460b29b5b89162@mail.gmail.com> Sorry I didn't see this list til now... I am here to help. -- Stephen J Smoogen. -- BSD/GNU/Linux How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" From smooge at gmail.com Fri Jun 13 23:22:33 2008 From: smooge at gmail.com (Stephen John Smoogen) Date: Fri, 13 Jun 2008 17:22:33 -0600 Subject: Best stab at questions Message-ID: <80d7e4090806131622r7c259119ic648ebc5cb5fc844@mail.gmail.com> I am playing ketchup, and saw these questions.. here are my take on them as EPEL Steering Committee head. Also note that while I use RHEL, I am meaning it as a short hand for Red Hat Enterprise Linux, CentOS, Scientific Linux, etal. > 1) How do appliances fit into EPEL? EPEL is meant to be a repository for extra packages that do not get shipped in EL but meet the 'same' packaging criteria as most Red Hat Enterprise Linux "Core" packages do. This means that using EPEL as a repository when building should help make integration easier. > 2) Is RPM a requirement for EPEL? Yes, all packages in EPEL are stored in RPM format. > 3) If we deploy to EPEL, do all of the packages we depend on need to be in EPEL as well? No. You could use packages in your appliance outside of EPEL, but in the case of 'conflicts' it could cause problems in integration or updates. Areas where I see packages not being in EPEL would be: a) Other propietary packages. b) Reliance on packages that do not meet EPEL's packaging structure (putting things in /opt. Requiring packages that are 'newer' than RHEL "Core" packages etc. > 3a) If so, who is responsible for getting those packages into EPEL? EPEL is a community project. We grow stronger with help and weaker without it. If your company would be better off by having someone spend some time a week making a package get into 'upstream' then you would be an excellent candidate to help. > 4) How is Fedora/Community prepared to help getting business applications into EPEL? Applications that are in EPEL need to meet Fedora's packaging standards plus RHEL standards. That means the code needs to be FLOSS and also not conflicting with items that RHEL ships intact. Thus if your application needs libwidget-1.7.1 and it is not in RHEL, and the code is GPL, BSD, MitX, Apache, and/or MPL (plus a long list Tom can go over) it can get included in EPEL. Then everyone else who needs libwidget can benefit and they can report/fix problems that may affect it. And you do not need to keep a separate package around in your code base with your own patches etc. A bad fit would be trying to include something that falls outside of Fedora/RHEL standards. Trying to get kmod-Win95 ( a GPL kernel module that loads in the windows 95 kernel) would not be ok since its outside of Fedora/RHEL standards being that it is a kernel driver . Another bad one would be a closed source code. > 4a) Are there FTEs devoted to getting business applications into EPEL? That is a Red Hat business decision I can't answer to. > 5) Do you need to go through Fedora to get to EPEL? Yes and no.. You need to sign the Fedora CLA and make sure the package meets Fedora packaging and licensing standards. There may also be some 'rough' spots where we work out how to get it into EPEL but not in Fedora proper if needed, but we will be filling out and testing those methods soon with some compat packages. -- Stephen J Smoogen. -- BSD/GNU/Linux How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" From jvenable at redhat.com Sat Jun 14 01:30:42 2008 From: jvenable at redhat.com (Jennifer Venable) Date: Fri, 13 Jun 2008 21:30:42 -0400 Subject: Late to the party... In-Reply-To: <80d7e4090806131522i7ac1bbc0tcf460b29b5b89162@mail.gmail.com> References: <80d7e4090806131522i7ac1bbc0tcf460b29b5b89162@mail.gmail.com> Message-ID: <48531F42.4030308@redhat.com> You're not late at all -- this list was just established a couple of weeks ago. Please let others know it's here! Stephen John Smoogen wrote: > Sorry I didn't see this list til now... I am here to help. > > -- ?Jennifer Venable Red Hat, Inc. 1801 Varsity Drive Raleigh, NC 27606 phone: 919-754-4096 fax: 919-754-3729 email: jvenable at redhat.com From mdahlman at jaspersoft.com Mon Jun 16 22:39:34 2008 From: mdahlman at jaspersoft.com (Matthew Dahlman) Date: Mon, 16 Jun 2008 15:39:34 -0700 (PDT) Subject: what do you want to know about EPEL? In-Reply-To: <1213283317.3866.234.camel@calliope.phig.org> References: <1213283317.3866.234.camel@calliope.phig.org> Message-ID: <003e01c8d001$da3525c0$750aa8c0@mdahlman2t60> Karsten, I'm a little late to the thread here, but I have a few thoughts to add. The approach that you've described sounds good. Explaining why one would want to do "whatever it takes to get software in to RPM" would be really useful for me. Likewise, it will be very useful for me to understand not just 'why' but also 'how'. The details of how to get software package X into RPM form are clearly beyond the scope of one session, but learning the high-level version of how to do this and documenting where to get further info would be great. I'd also like to learn clear definitions of what it means for a package to "be in EPEL" and to "be in Fedora". It seems simple enough... but then I try to explain it to someone else and find that I can't explain it precisely. If I can't explain it well, then I guess I didn't know it well in the first place. Actually, it's perhaps useful if I explain my position. Maybe others are in similar situations. My company has relatively little experience with Fedora, but we're very interested in learning about getting our JasperServer product into EPEL. I'd love to get a better feel for what skills we need to do this. I don't have RPM experience, what sites or books might help bring me up to speed quickest in this area? Our app needs an app server; how should I lookup what app servers are already supported in Fedora? Same for databases. I guess by the nature of your talk you would start with questions like, "What is EPEL?". For me, I'd certainly like it if you start with simple questions like this just to make sure that we all have the same foundational knowledge. I began by reading "(EPEL) is a volunteer-based community effort from the Fedora project to create a repository of high-quality add-on packages that complement ..." While this is no doubt accurate, I didn't find it intuitively clear. Covering basic things like this in the session would be great. Regards, Matt Dahlman JasperSoft -----Original Message----- From: fedora-isv-sig-list-bounces at redhat.com [mailto:fedora-isv-sig-list-bounces at redhat.com] On Behalf Of Karsten 'quaid' Wade Sent: Thursday, 12 June, 2008 8:09 To: fedora-isv-sig-list at redhat.com Subject: what do you want to know about EPEL? I'm doing the final work on my presentation on EPEL[1] at the Red Hat Summit, and I'm wondering if there any questions you all have I should address? Generally, the approach is to describe what EPEL is (and what it isn't), and the various reasons why it is an important enough goal to warrant doing whatever it takes to get software in to RPM. Also, I'm going to touch upon some of the new work we are doing to enable ISVs to be successful -- this SIG, the other sessions at the Summit and FUDCon, etc. Let me know if there is anything you'd want to hear more of, less of, etc. thx - Karsten [1] https://fedoraproject.org/wiki/EPEL -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 From kwade at redhat.com Tue Jun 17 11:39:51 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Tue, 17 Jun 2008 04:39:51 -0700 Subject: what do you want to know about EPEL? In-Reply-To: <4493757.1621213283936872.JavaMail.lfaus@lee-imac.local> References: <4493757.1621213283936872.JavaMail.lfaus@lee-imac.local> Message-ID: <1213702791.8326.52.camel@calliope.phig.org> On Thu, 2008-06-12 at 16:18 +0100, Lee Faus wrote: > When is you talk? Sorry, missed that I still had a question out there. :) I'm scheduled[1] for Thursday, 2:45 pm, in the OSS track. Thanks for the input everyone. - Karsten [1] http://www.redhat.com/promo/summit/2008/agenda/schedule.html -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From kwade at redhat.com Thu Jun 26 13:01:06 2008 From: kwade at redhat.com (Karsten 'quaid' Wade) Date: Thu, 26 Jun 2008 06:01:06 -0700 Subject: Best stab at questions In-Reply-To: <80d7e4090806131622r7c259119ic648ebc5cb5fc844@mail.gmail.com> References: <80d7e4090806131622r7c259119ic648ebc5cb5fc844@mail.gmail.com> Message-ID: <1214485266.8374.33.camel@calliope.phig.org> After working through these questions (which did help the presentation[1]), I wanted to highlight these conflicting answers as an example of what is confusing about the packaging process. The key to the answer is the phrase "depends on". Stephen uses it one context and Tom another. Here is how I am addressing it: Note: add-on packages that are not dependencies can exist outside of EPEL, since they are not needed to build the package from source or to support package installation, such as system libraries. An example of this is an open source game engine and a set of game levels that are not free and open content. The game engine can be built and installed by itself without any level, for example, so someone can build free and open levels. The levels make for a nicer playing experience, but are not required, and could be in an external repository. On Fri, 2008-06-13 at 17:22 -0600, Stephen John Smoogen wrote: > > 3) If we deploy to EPEL, do all of the packages we depend on need to be in EPEL as well? > > No. You could use packages in your appliance outside of EPEL, but in > the case of 'conflicts' it could cause problems in integration or > updates. Areas where I see packages not being in EPEL would be: > > a) Other propietary packages. > b) Reliance on packages that do not meet EPEL's packaging structure > (putting things in /opt. Requiring packages that are 'newer' than RHEL > "Core" packages etc. ... and ... On Thu, 2008-06-12 at 11:29 -0400, Tom "spot" Callaway wrote: > > > 3) If we deploy to EPEL, do all of the packages we depend on need to > > be in EPEL as well? > > Yes. Short answers -- all package dependencies must be in EPEL (or RHEL), but not all things you might "depend on." - Karsten [1] I'll post more about this presentation later, but here are the pieces; the PDF includes notes, which are also found in the 'script' file: http://quaid.fedorapeople.org/presentations/Red-Hat-Summit-2008/Summit08_Presentation-kwade-1.1.pdf http://quaid.fedorapeople.org/presentations/Red-Hat-Summit-2008/Summit08_Presentation-script-1.0.txt -- Karsten Wade, Sr. Developer Community Mgr. Dev Fu : http://developer.redhatmagazine.com Fedora : http://quaid.fedorapeople.org gpg key : AD0E0C41 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: