Menu

#3929 TeXworks version 0.3 package

closed
nobody
5
2011-05-31
2011-02-21
Prerna Atri
No

Does this package have OS version restrictions? Yes. 10.6.
Which section does it belong in? editors
Have you built it with -m --build-as-nobody? Yes.

To avoid possible failure due to circular dependeny between glib2, shared-mime-info and gtk:
1. Build glib2 library without -m before texwoks build.
OR
2. Install Fink package destop-file-utils before texworks build.

Discussion

1 2 3 > >> (Page 1 of 3)
  • Prerna Atri

    Prerna Atri - 2011-02-21

    TeXworks version 0.3 .info file

     
  • Alexander Hansen

    Follow the standard naming conventions for our qt packages. Name this
    texworks-mac, to allow for the possibility of a qt4-x11 version.

    Don't bother with that DescPackaging note. That's not a problem which
    _this_ package specifically needs to address.

    Why are you creating %i/bin %i/lib/texworks when you don't install
    anything in those directories?

    Instead of copying the app bundle manually, why not use an AppBundles field?

    Similarly, copying the README and COPYING files manually isn't
    necessary. That's what the DocFiles Field is for.

    You probably need a BuildDepends: system-java-dev (>=1.6-0), since you
    Depend on system-java (>=1.6-0)

    Your Depends are totally inadequate. Why do you have a Depend on
    pkgconfig, which is normally needed only at build time? If you
    BuildDepend on qt4-mac, you have to Depend on the corresponding shared
    library packages. Similarly for poppler4-qt-mac.

     
  • Alexander Hansen

    You didn't mark the package as Architecture: x86_64,
    even though you have "xcodebuild ARCHS=x86_64". Nor do you note a Distribution: restriction, even though you say above that there is an OS version restriction.

     
  • Alexander Hansen

    Please remember to set the Group field to "Undergoing
    Validation" when you create a new Tracker item and
    any time you update your submission and are waiting
    for feedback. Thanks.

     
  • Alexander Hansen

    • milestone: --> 373614
     
  • Prerna Atri

    Prerna Atri - 2011-02-25

    texworks-mac info file

     
  • Prerna Atri

    Prerna Atri - 2011-02-25
    • milestone: 373614 --> 373615
     
  • Prerna Atri

    Prerna Atri - 2011-02-25

    texworks-mac.info file added with the suggested changes. Please review.

     
  • Alexander Hansen

    Is there a reason that it needs to be only for OS 10.6 and x86_64? It's not that hard to feed a different architecture to xcodebuild.

     
  • Alexander Hansen

    Fiona-2:~ hansen$ fink -l -m --build-as-nobody build texworks-mac
    Scanning package description files..........
    Information about 9803 packages read in 7 seconds.
    Running in Maintainer Mode
    Validating package file /sw64/fink/dists/local/main/finkinfo/texworks-mac.info...
    Error: Info file has DOS line endings. (/sw64/fink/dists/local/main/finkinfo/texworks-mac.info)
    Failed: Please correct the above problems and try again!

     
  • Alexander Hansen

    • milestone: 373615 --> 373614
     
  • Alexander Hansen

    sudo -u fink-bld [ENV] sh -c/var/tmp/tmp.15.Fw2WOy
    /var/tmp/tmp.0.CsjPCX
    #! /bin/sh -ev
    qmake
    /var/tmp/tmp.0.CsjPCX: line 2: qmake: command not found
    ### execution of /var/tmp/tmp.0.CsjPCX failed, exit code 127

    qmake from QT4 isn't in the PATH by default:

    $ dpkg -S bin/qmake
    qt4-x11: /sw64/lib/qt4-x11/bin/qmake
    qt4-mac: /sw64/lib/qt4-mac/bin/qmake

    Fix that.

     
  • Alexander Hansen

    • status: open --> closed-invalid
     
  • Alexander Hansen

    You appear not to have tested this at all, much less with --m --build-as-nobody, since your CompileScript would never have worked on any system.

    I am therefore closing this item. This tracker is intended for packages that at least build on the submitter's system, and for people who honestly attempt to run "fink -m --build-as-nobody build" on their submissions.

    We can try again once you have something that at least can attempt to work properly on your end.

     
  • Alexander Hansen

    • milestone: 373614 --> 1837387
     
  • Prerna Atri

    Prerna Atri - 2011-02-26

    We had submitted after testing it on our system. We were able to build and install TeXworks successfully. We are not sure why the build errors are being seen at your end. We shall however try to build it on another system and resubmit after testing on it.

     
  • Alexander Hansen

    OK. Perhaps I jumped to an unwarranted conclusion.

    If your test system has, for example, a symbolic link from /sw/bin/qmake to /sw/opt/lib/kde4-mac/bin/qmake, that would allow you just to use "qmake" in your CompileScript. That's still not correct for packaging purposes.

     
  • Alexander Hansen

    • milestone: 1837387 --> 373614
    • status: closed-invalid --> open-invalid
     
  • Alexander Hansen

    oops, that should have been

    /sw/opt/kde4/mac/bin/qmake .

     
  • Alexander Hansen

    • status: open-invalid --> open
     
  • Prerna Atri

    Prerna Atri - 2011-04-18

    Updated info file.

     
  • Prerna Atri

    Prerna Atri - 2011-04-18

    The info file has been modified with required path settings.

     
  • Prerna Atri

    Prerna Atri - 2011-04-18
    • milestone: 373614 --> 373615
     
  • Alexander Hansen

    Your current .info file doesn't work:

    $ fink -l -m --build-as-nobody build texworksScanning package description files..........
    Information about 9926 packages read in 2 seconds.
    Running in Maintainer Mode
    Validating package file /sw64/fink/dists/local/main/finkinfo/texworks-mac.info...
    Warning: Incorrect filename 'texworks-mac.info'. Should be one of:
    texworks.info
    texworks-0.3.info
    texworks-0.3-1.info
    Failed: Please correct the above problems and try again!

    Package: texworks
    Version: 0.3
    Revision: 1

     
  • Alexander Hansen

    Your Source is not acceptable. Use the developers' original source, and make any modifications within your .info file (and .patch file, if needed).

     
1 2 3 > >> (Page 1 of 3)

Log in to post a comment.