#2 bdist_rpm target doesn't work

open-out-of-date
nobody
None
5
2007-02-22
2005-10-11
No

The way things get packed up for bdist_rpm is a little
odd. It only includes files it knows to, so you have
to specify non-compiled files in MANIFEST.in (or at
least that is the easiest way). I put this in a
MANIFEST.in file at the root of the distribution, and
it works grand:

include scintilla/include/*.h
include scintilla/src/*.h
include PySilverCity/Src/*.h
include Lib/Src/*.h
include CSS/*.css

Now it packages those files when building the temporary
tarball before building an RPM, and compile and
packaging doesn't fail.

Discussion

  • Brian Quinlan

    Brian Quinlan - 2006-11-23

    Logged In: YES
    user_id=108973
    Originator: NO

    If you are still interested in RPM build, could you try this with SilverCity 0.97 and send me your modified MANIFEST.in file?

     
  • Brian Quinlan

    Brian Quinlan - 2006-11-23
    • status: open --> closed-out-of-date
     
  • Kyle VanderBeek

    Kyle VanderBeek - 2007-02-22
    • status: closed-out-of-date --> open-out-of-date
     
  • Kyle VanderBeek

    Kyle VanderBeek - 2007-02-22

    MANIFEST.in that makes bdist_rpm target work.

     
  • Kyle VanderBeek

    Kyle VanderBeek - 2007-02-22

    Logged In: YES
    user_id=51762
    Originator: YES

    The bdist_rpm build target can't find some of the header files. Just remove the MANIFEST and replace it with the MANIFEST.in I'm providing, and it'll auto-generate the right MANIFEST.
    File Added: MANIFEST.in

     
  • Brian Quinlan

    Brian Quinlan - 2007-02-23

    Logged In: YES
    user_id=108973
    Originator: NO

    There is already MANIFEST.in at that directory level in svn. The problem seems to be that it doesn't get included in source distribution. If I add MANIFEST.in to MANIFEST.in, will the source distribution work for you?

     
  • Kyle VanderBeek

    Kyle VanderBeek - 2007-02-23

    Logged In: YES
    user_id=51762
    Originator: YES

    For some reason, the MANIFEST that gets generated by "sdist" isn't the same as the one that gets generated otherwise. Having pulled from SVN and overlayed scintilla (also from SVN), "bdist_rpm" works fine. However, if I do a "sdist" and try to then do a "bdist_rpm" from the resulting tarball, it breaks.

    There seems to be some considerable cruft in MANIFEST.in. I'll try to get it working and submit a patch.

     
  • Kyle VanderBeek

    Kyle VanderBeek - 2007-03-01

    Logged In: YES
    user_id=51762
    Originator: YES

    Turns out you just need this added to MANIFEST.in

    include MANIFEST.in

    There have been some suggestions made to the distutils maintainers to make this the default, but that hasn't happened. This will allow any/all bdist type targets to be generated from a sdist tarball.

     
  • Kyle VanderBeek

    Kyle VanderBeek - 2007-03-01

    Logged In: YES
    user_id=51762
    Originator: YES

    Semi-related, you may want to clean up the MANIFEST.in to eliminate these warnings:

    warning: no files found matching '*.hpp' under directory 'PySilverCity/Src'
    warning: no files found matching '*.hpp' under directory 'Lib/Src'
    warning: no files found matching '*.py' under directory 'Lib/Src'
    warning: no files found matching '*.hpp' under directory 'scintilla/src'
    warning: no files found matching '*.hpp' under directory 'scintilla/include'
    warning: no files found matching '*.py' under directory 'Scripts'
    warning: no files found matching '*.html' under directory 'Scripts/styler-templates'

    Some of those directories don't even exists anymore.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks