The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)


Search results

From Mer Wiki
Jump to: navigation, search

Page title matches

  • = Packaging Guidelines = ...' number which should be manually incremented by the maintainer whenever a packaging changes (this includes changing a patch)
    35 KB (5,469 words) - 23:20, 13 June 2013
  • == Packaging with gem2rpm == ...it is time to add files, add new entry to .changes file and upload the new packaging.
    5 KB (743 words) - 23:15, 25 October 2012
  • ...e-hg</code> for integrating the upstream Mercurial repository into our Git packaging repository. === Packaging new upstream releases ===
    3 KB (481 words) - 11:57, 21 April 2014
  • ... this guide the binary called specify is used to ease the start of the rpm packaging. List of source files one has in packaging. NOTE: patches have separate section.
    3 KB (361 words) - 16:34, 24 October 2012
  • 2 KB (261 words) - 09:45, 18 July 2013
  • ...added the project to the list of disabled webhook projects so only the git packaging service will run and that will use a fixed commit.
    4 KB (657 words) - 11:54, 2 January 2015

Page text matches

  • *** Mer packaging for closed source SGX drivers: http://repo.pub.meego.com/home:/harbaum:/ti- ...y on a c compiler, it is of use on hardware for which no UI is available. (packaging in progress)
    9 KB (1,400 words) - 20:35, 7 January 2015
  • If you like code, packaging, and are interested in contributing to the project code development take a
    6 KB (929 words) - 08:18, 27 May 2017
  • == Add source/packaging == Now you have a new set of packaging
    14 KB (2,391 words) - 20:48, 19 June 2016
  • === Step V: Validate packaging === Validate proposed changes + packaging as being OK
    3 KB (457 words) - 18:39, 23 December 2011
  • * Packaging checks === Packaging checks ===
    11 KB (1,667 words) - 16:40, 27 October 2012
  • * [[Nemo/Development | Guide for Development]], git trees, code, example git packaging, etc.
    7 KB (932 words) - 11:58, 19 September 2018
  • # Modify packaging You can now edit the code and packaging
    10 KB (1,711 words) - 10:36, 5 November 2015
  • == Packaging == sudo yum install meego-packaging* --nogpgcheck
    1 KB (208 words) - 10:53, 8 February 2012
  • ... release requires reliable version control of both the code and associated packaging. This is not yet implemented and the interim solution is to publish the OBS
    8 KB (1,253 words) - 21:34, 27 June 2016
  • = Packaging Guidelines = ...' number which should be manually incremented by the maintainer whenever a packaging changes (this includes changing a patch)
    35 KB (5,469 words) - 23:20, 13 June 2013
  • Scratchbox2 packaging: http://gitweb.merproject.org/gitweb?p=mer-core/scratchbox2.git;a=tree Fakeroot packaging: http://gitweb.merproject.org/gitweb?p=mer-core/fakeroot.git;a=tree
    13 KB (2,027 words) - 11:51, 22 October 2014
  • The package is called mer-kernel-checks, which is also used in the kernel packaging template
    2 KB (313 words) - 13:00, 29 January 2013
  • === Packaging ===
    16 KB (2,476 words) - 20:41, 24 June 2016
  • After this we have the very basic structure and files for the kernel packaging. graphics are expected. For this there is a template packaging available at
    14 KB (2,171 words) - 16:51, 27 June 2013
  • Spectacle is the toolset for packaging maintenance from Mer, including the tool For spectacle managed packages, all generic packaging information will be stored
    14 KB (1,828 words) - 17:44, 10 August 2013
  • * The packaging effort can be followed here : https://build.pub.meego.com/project/subprojec * The packaging of dependencies are mostly reused from Fedora, but while tryin to reduce un
    3 KB (408 words) - 10:35, 1 February 2012
  • Step five is to rebuild and refresh the packaging system so we can install devel packages:
    9 KB (1,384 words) - 23:46, 16 February 2014
  • Test packaging is the mechanism to wrap any tests in rpm packages for manual and automatic
    3 KB (529 words) - 12:45, 13 April 2012
  • ** Test packaging was used, the naming policy was strict
    3 KB (517 words) - 16:34, 6 May 2012
  • Fedora packaging snippets: https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd also http://www.freedesktop.org/software/systemd/
    2 KB (224 words) - 13:25, 18 June 2013
  • == Packaging with gem2rpm == ...it is time to add files, add new entry to .changes file and upload the new packaging.
    5 KB (743 words) - 23:15, 25 October 2012
  • ...bout projects and packages and downloading/uploading their source code and packaging
    5 KB (713 words) - 09:56, 23 March 2014
  • ...can be found from https://github.com/nemomobile Each repo project contains packaging information which is using the [[Nemo/Development#With_tar_git_service|tar_ The ''nemomobile-packages'' is meant only for packaging information for packages which contain upstream somewhere else and can be f
    11 KB (1,737 words) - 16:32, 1 June 2015
  • == Packaging == Packaging development project:
    12 KB (1,830 words) - 19:09, 15 June 2014
  • ...e-hg</code> for integrating the upstream Mercurial repository into our Git packaging repository. === Packaging new upstream releases ===
    3 KB (481 words) - 11:57, 21 April 2014
  • === rpm packaging ===
    4 KB (713 words) - 12:19, 16 December 2013
  • ... this guide the binary called specify is used to ease the start of the rpm packaging. List of source files one has in packaging. NOTE: patches have separate section.
    3 KB (361 words) - 16:34, 24 October 2012
  • ** NOTE: because of Nokia Store packaging requirements, the necessary parts of the Communi library are embedded into
    3 KB (418 words) - 20:48, 10 November 2012
  • Step five is to rebuild and refresh the packaging system so we can install devel packages:
    3 KB (479 words) - 14:06, 5 February 2013
  • Mer Project packaging in git project. ...of the tarball in git it was quite straightforward to turn it into tar_git packaging, sample result: https://github.com/mer-tools/sudo/tree/mer-unified-master
    3 KB (384 words) - 12:17, 28 February 2017
  • ...king advantage of this to (where possible) do ports in-place by adding qt5 packaging, and hacking the build system and code to handle that conditionally where p = Packaging setup =
    9 KB (1,213 words) - 12:25, 2 August 2013
  • === Packaging === === Packaging Metadata ===
    8 KB (1,221 words) - 13:48, 1 July 2013
  • * Edit code, packaging files, whatever you want
    4 KB (627 words) - 11:39, 23 May 2014
  • | nemo-qml-plugin-folderlistmodel||PORTED BUT NEED Qt5 PACKAGING
    10 KB (1,392 words) - 14:12, 8 January 2014
  • .../html/Packagers_Guide/sect-Packagers_Guide-Creating_a_Basic_Spec_File.html packaging] technologies
    522 B (73 words) - 13:09, 5 May 2014
  • * (tech bubbles:) Before Alpha10, porting underwent an important packaging reorg, which will make adaptation for future devices even easier and less c
    9 KB (1,345 words) - 14:41, 23 October 2017
  • ...added the project to the list of disabled webhook projects so only the git packaging service will run and that will use a fixed commit.
    4 KB (657 words) - 11:54, 2 January 2015
  • How to create webhooks: https://wiki.merproject.org/wiki/Packaging/webhooks ...ey.x509.pem > /home/$USER/mer/android/droid/out/target/product/$DEVICE/obj/PACKAGING/ota_keys_intermediates/keys
    44 KB (6,843 words) - 11:35, 23 September 2019

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

Views
Personal tools