packaging November 2008

packaging@lists.fedoraproject.org

25 participants
15 discussions

Vim compile options in Fedora
by Timandahaf 12 Nov '08

12 Nov '08

Hello, In the past few versions of Fedora, the Vim package (for instance, vim-enhanced 2:7.1.291-1.fc9) is compiled with the "clientserver" option turned off. So each time I upgrade, I'm forced to get the rpm source and recompile vim with this option turned on. I don't know the rationale for this, because this is a very useful option, and turning it on doesn't really come at any cost as far as I know. I suspect this option would be useful for a wider range of users too. (For more info, simply start up vim by typing "vim" and use the ":version" command. It lists the features vim was compiled with.) My question is, how do I go about placing a request to have this feature turned on? (I apologize in advance if this is not the appropriate list to ask this question.) Thanks in advance!

2 1

patching datafile locations for upstream projects ?
by Jani Mikkonen 12 Nov '08

12 Nov '08

Hello. Say, i have few packages - mostly games - that rely that same datafiles that are found from cwd (or same path as executable as binary) and im wondering what is the right way to patch these so i could make functional packages out of them. 1) just force the pwd to the datadirectory in .desktop file and not patch the code 2) hardcode the paths or atleast make them defineable at compiletime ? 3) something else ?

2 1

Hi all!
by Uwe Kubosch 11 Nov '08

11 Nov '08

Hi all! I have just submitted zfs-fuse to Fedora and i am looking forward to further contributing to Fedora! When can I expect .fc10 packages to be signed? After Fedora 10 release on the 25th? -- With kind regards, Uwe Kubosch Norway

1 0

Hi
by gnu boi 09 Nov '08

09 Nov '08

hi to all

2 1

Packaging rubygem-passenger and "mod_rails"
by Jeroen van Meeuwen 09 Nov '08

09 Nov '08

Hi all, I'm interested in some feedback and hints as to how to tackle this problem I'm seeing: rubygem-passenger upstream is a Ruby on Rails deployment utility that practically makes installing a new version of a Ruby on Rails web application a drag-and-drop action. Anyway; One part of the upstream release is the Ruby Gem - which, when installed, offers a command that says; passenger-install-apache2-module which is mod_rails/mod_rack, and can be loaded in httpd so that it's all nice and integrated and nifty. Problem is, "passenger-install-apache2-module" is building the .so and now I'm seeing a chicken-or-egg problem; I need the gem to be installed to be able to build the httpd module, and the httpd module is built from the same source(s). I would appreciate some advice as to if splitting the packages and build-requiring the rubygem-passenger package for the mod_rails package is the way to go, or whether there's another route. Thanks in advance, Kind regards, Jeroen van Meeuwen -kanarip

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

packaging November 2008