Re: Re: New PHP extension

If the headers are GPL, then his code will be GPL'd. If he's linking against librpm, then his code will be GPL'd. :-( Andrew: GPL is "bad" because the license is all about the freedom of the code (at the expense of the freedom of the people using the code). PHP uses a license grants freedom for people to use the code. The two are incompatible both legally and philosophically, and that is the reason that we cannot host GPL'd packages in PECL. --Wez On 8/26/05, Dan Scott <denials@gmail.com> wrote: > On 8/25/05, Wez Furlong <kingwez@gmail.com> wrote: > > Sadly, rpm is a GPL'd project so we can't take it into PECL. > > > > --Wez. > > Does this restriction apply even if Andrew's implementation just pulls > the headers from the RPM file without using any GPLed libraries? > > Dan > > > > > On 8/25/05, Sara Golemon <pollita@php.net> wrote: > > > > I have been working on a new PHP extension > > > > that I haven't been able to find anywhere else. > > > > I have called it 'rpmfile' and it basically reads the > > > > headers from an RPM (Redhat Package > > > > Management) file and will return to PHP any > > > > one of the numerous values therein. I have not > > > > designed it to do anything further than read-only > > > > access to an RPM file as of yet. I would like > > > > to publish it through PECL, but I wanted to > > > > know what the process was. Please let me know. > > > > > > > You just covered step 1 -- Introducing yourself and your project to the > > > list. For what my oppinion matters, it sounds like a good PECL candidate. > > > My only question would be: What about this extension requires an internal > > > implementation? (I sounds like something which could be done in userspace > > > via a PEAR class and would therefore be more universally usable by end > > > users, especially those on shared hosting providers) > > > > > > Step 2 is putting together a working extension -- feel free to ask for help > > > on this list on specific implementation details. > > > > > > Step 3: Since you're new, you should post the extension somewhere that it > > > can be downloaded and reviewed prior to submission. > > > > > > Step 4: While your code is being reviewed, submit a PECL account request, be > > > sure to ask for CVS access as well. > > > > > > Step 5: When you've gotten the thumbs up (in the form of your account > > > request being granted, you can create the package entry, upload your first > > > release, and (optionally -- though preferred) check your extension into CVS > > > (this will also permit automatic building by snaps.php.net) > > > > > > -Sara > > > > > > -- > > > PECL development discussion Mailing List (http://pecl.php.net/) > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > -- > > PECL development discussion Mailing List (http://pecl.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > -- > PECL development discussion Mailing List (http://pecl.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >