Hi,
I am planning to package funnel[0], a software for online submissions
and voting of talks as part of the FUDCon India effort but I am not
familiar with the structure of wsgi. Can someone please give me
guidance on how to package this source.
[0] https://github.com/hasgeek/funnel
Thanks and
> I am packaging a program that has two front ends, one for Gtk and other for
> Qt.
> Is there a standard packaging structure to handle such packages?
> I see two methods to do this :
>
> 1. Use an empty "meta" package that pulls in a default (gtk) front end. E.g
> :
> Pname (meta) -> Pname-common
On Sat, Jul 23, 2011 at 02:00:24PM -0700, Douglas Myers–Turnbull wrote:
> Hi,
>
> Just something I wanted to bring to attention:
>
> Java 7 is slated for release (after years of hassle and heated debate)
> on 28 July, 2011.
> I think this would be an important feature to include for the Fedora
>
On Sat, Jul 23, 2011 at 4:58 PM, Paul Howarth wrote:
> The python interpreter expects to find all parts of a module in the
> same directory, so if there are C bits, everything goes in
> %{python_sitearch}.
Thanks! That's what I needed! I'm trying to fix a package which is C
based but has python w
On Sat, 23 Jul 2011 16:26:34 -0500
Richard Shaw wrote:
> I was reviewing the guidelines and maybe I'm over thinking things but
> one part that doesn't seem to be clear...
>
> Ok I understand that if you have a pure python module it goes in
> %{python_sitelib} (/usr/lib) and if you have a C exten
I was reviewing the guidelines and maybe I'm over thinking things but
one part that doesn't seem to be clear...
Ok I understand that if you have a pure python module it goes in
%{python_sitelib} (/usr/lib) and if you have a C extension module it
goes in %{python_sitearch} (/usr/lib for 32bit or /u
Hi,
Just something I wanted to bring to attention:
Java 7 is slated for release (after years of hassle and heated debate)
on 28 July, 2011.
I think this would be an important feature to include for the Fedora
16 release, and the months between Java's release and Fedora 16's 25
October release wou
On Sat, 2011-07-23 at 00:09 +, "Jóhann B. Guðmundsson" wrote:
> On 07/22/2011 05:02 PM, Ric Wheeler wrote:
> > I don't have it backwards - my day job is to work on exactly getting
> > this kind of cutting edge feature out to end users.
>
> Which feature of this magnitute have you put out t
first i changed the topic because it does not fit
anly longer to this thread
Am 23.07.2011 03:41, schrieb Adam Williamson:
> On Thu, 2011-07-21 at 13:38 +0200, Reindl Harald wrote:
>
>> in the past there were real developers which was able to
>
> ah, the True Scotsman rears its head!
if you are
On Sat, Jul 23, 2011 at 9:18 PM, Raghu Siddarth wrote:
> Hello,
>
> I am packaging a program that has two front ends, one for Gtk and other for
> Qt.
>
> Is there a standard packaging structure to handle such packages?
I guess you can take a look at how "transmission" does this...
>
> I see two
Hello everybody,
I am Olivier from France. I work now as a System/Network Architect in
the Spatial domain especially in Satellite telecommunications. I work
every day on Linux Platform especially Fedora / Redhat / CentOS platform
doing software and hardware integration, architecture and packagi
Hello,
I am packaging a program that has two front ends, one for Gtk and other for
Qt.
Is there a standard packaging structure to handle such packages?
I see two methods to do this :
1. Use an empty "meta" package that pulls in a default (gtk) front end. E.g
:
Pname (meta) -> Pname-common -> P
On 07/23/2011 11:24 AM, Ric Wheeler wrote:
>
>
> What I think that you and others are not given credit is that most
> upstream maintainers have very long lists of things to do. The NFS
> team is swamped doing support for pNFS (version 4.1) and has been
> going through massive change for example.
On Thu, 21 Jul 2011 18:58:13 +0400, DB (Dmitry) wrote:
> There is "fedora-icon-theme" package, which looks strange a little.
>
> Since F13 it no more contains any files at all (just directories), ie.
> it looks like a meta-package.
> OTOH its source rpm still has full tarball with png icons etc.
What I think that you and others are not given credit is that most upstream
maintainers have very long lists of things to do. The NFS team is swamped doing
support for pNFS (version 4.1) and has been going through massive change for
example.
When you have a very invasive feature that requires
On 07/22/2011 10:33 PM, Toshio Kuratomi wrote:
> The rpm changelog can reasonably be in any timezone.
It is better to always write the changelog timestamp in UTC to avoid
"%changelog not in descending chronological order" build errors if the
specfile is modified at unfortunate moments in differen
16 matches
Mail list logo
