recentpopularlog in

kme : packaging   67

SPDX License List | Software Package Data Exchange (SPDX)
These are the identifiers recognized in NPM's 'package.json' files.
npm  package.json  opensource  license  licensing  packaging  reference 
december 2019 by kme
Creating a package.json file | npm Documentation
<code class="language-json">{
"name": "my-awesome-package",
"version": "1.0.0"
}</code>

or:
<code class="language-bash">npm init</code>
webdevel  javascript  npm  packaging  dammitbrain  solution 
december 2019 by kme
PEP 440 -- Version Identification and Dependency Specification | Python.org
For a given release identifier V.N, the compatible release clause is approximately equivalent to the pair of comparison clauses:

>= V.N, == V.*

This operator MUST NOT be used with a single segment version number such as ~=1.

For example, the following groups of version clauses are equivalent:

~= 2.2
>= 2.2, == 2.*

~= 1.4.5
>= 1.4.5, == 1.4.*
python  pip  semver  packaging  versionpinning  pinning  versioning  dependency  reference  dammitbrain 
october 2019 by kme
Getting Started With setuptools and setup.py — an_example_pypi_project v0.0.5 documentation
<code class="language-python">import os
from setuptools import setup

# Utility function to read the README file.
# Used for the long_description. It's nice, because now 1) we have a top level
# README file and 2) it's easier to type in the README file than to put a raw
# string in below ...
def read(fname):
return open(os.path.join(os.path.dirname(__file__), fname)).read()

setup(
name = "an_example_pypi_project",
version = "0.0.4",
author = "Andrew Carter",
author_email = "andrewjcarter@gmail.com",
description = ("An demonstration of how to create, document, and publish "
"to the cheese shop a5 pypi.org."),
license = "BSD",
keywords = "example documentation tutorial",
url = "http://packages.python.org/an_example_pypi_project",
packages=['an_example_pypi_project', 'tests'],
long_description=read('README'),
classifiers=[
"Development Status :: 3 - Alpha",
"Topic :: Utilities",
"License :: OSI Approved :: BSD License",
],
)</code>
python  install  setup.py  setuptools  packaging  template  dammitbrain 
october 2019 by kme
python - Setuptools "development" Requirements - Stack Overflow
So using
<code class="language-python">setup({
install_requires=requirements,
extras_require={
'dev': [
'pytest',
'pytest-pep8',
'pytest-cov'
]
}
})</code>

And then
<code class="language-bash">pip install -e .[dev]</code>

seems to be best practice.
python  setuptools  packaging  virtualenv  solution  bestpractice 
june 2019 by kme
git_semver · PyPI
Simple usage
<code class="language-bash">git semver
# 0.1.0

git semver --next-patch
# 0.1.1

git semver --next-minor
# 0.2.0

git semver --next-major
#1.0.0</code>
devel  git  semver  versioning  packaging  release  utility  python  helperscript 
june 2019 by kme
python - How can I get the version defined in setup.py (setuptools) in my package? - Stack Overflow
<code class="language-python">import pkg_resources # part of setuptools
version = pkg_resources.require("MyProject")[0].version</code>
python  setuptools  packaging  solution 
june 2019 by kme
Adding custom commands to setup.py
This was implemented in b682a380 of seq-core-ngs-downloader.
python  setuptools  setup.py  installation  setup  customization  packaging  release  automation 
june 2019 by kme
Deciphering Glyph :: Software You Can Use
The worse news is that every day we don’t have this, more and more people are re-writing their user-facing tools and applications in JavaScript or Go or Swift or Java, to suit their target platform, because it is honestly easier to learn an entirely new programming language and toolchain, and rewrite an entire application than to figure out how to build a self-contained executable in Python right now.
python  sorrystateof  desktop  devel  packaging 
june 2019 by kme
GitHub - h2non/nar: node.js application archive - create self-contained binary like executable applications that are ready to ship and run
node.js application archive - create self-contained binary like executable applications that are ready to ship and run - h2non/nar
shroudedscript  shrouding  javascript  nodejs  commandline  packaging 
june 2019 by kme
Deciphering Glyph :: Tips And Tricks for Shipping a PyGame App on the Mac
Luckily the OS ships with the macOS-specific “scriptable image processing system”, which can helpfully convert an icon for you. Make yourself a 512x512 PNG file in your favorite image editor (with an alpha channel!) that you want to use as your icon, then run it something like this:
<code class="language-bash">$ sips -s format icns Icon.png --out Icon.icns</code>
somewhere in your build process, to produce an icon in the appropriate format.
mac  python  pygame  packaging  woes  imageprocessing  icons  tipsandtricks 
june 2019 by kme
python - No module named pkg_resources - Stack Overflow | https://stackoverflow.com/
None of these worked.

What I ended up doing was:

<code class="language-bash">
curl -O https://bootstrap.pypa.io/get-pip.py
python3 get-pip.py --user
rm ~/.local/bin/pip # so the distro pip for Python 2.7 takes precedence
</code>
python  errormessage  annoyance  packaging  pip  ubuntu  16.04  workaround  solution 
february 2019 by kme
installation - ImportError: module 'setuptools.dist' has no 'check_specifier' attribute - Stack Overflow | https://stackoverflow.com/
It was due to older setuptools version. I updated setuptools as follows:
<code class="language-bash">sudo pip install setuptools --upgrade</code>

It installed setuptools-31.0.0 and that worked.
pip  python  centos6  errormessage  packaging  installation  solution 
november 2018 by kme
package.json | npm Documentation | https://docs.npmjs.com/
Bare minimum valid 'package.json':

<code class="language-javascript">
{
"url" : "https://github.com/owner/project/issues",
"email" : "project@hostname.com"
}
</code>
npm  package.json  packaging  webdevel  dammitbrain  reference 
november 2017 by kme
Debian Policy Manual v4.1.1.1 - https://www.debian.org/
5.6.12 Version

The version number of a package. The format is: [epoch:]upstream_version[-debian_revision].

The three components here are:

epoch
This is a single (generally small) unsigned integer. It may be omitted, in which case zero is assumed. If it is omitted then the upstream_version may not contain any colons.

It is provided to allow mistakes in the version numbers of older versions of a package, and also a package’s previous version numbering schemes, to be left behind.
debian  dpkg  packaging  packagemanagement  versioning  version  specification  reference  solution 
october 2017 by kme
python - setuptools and pip: choice of minimal and complete install - Stack Overflow
Turns out Dask uses these, so if you want the dask.dataframe, you have to do 'pip install dask[dataframe]'.
python  pip  packaging  installation  solution 
january 2017 by kme
Writing PERL Packages & Modules
You will run into problems if you do this while also doing 'use strict;'. One solution is to declare any package-level exportable variables as well as '@ISA' and so forth using 'our'.
package Module;

require Exporter;
@ISA = qw(Exporter);
@EXPORT = qw(bar blat);


An alternative solution (using 'use vars'): http://www.xinotes.net/notes/note/176/
perl  module  package  packaging  howto  newbie  tutorial 
december 2016 by kme
Debian Policy Manual - Control files and their fields
5.6.12 Version

The version number of a package. The format is: [epoch:]upstream_version[-debian_revision]


The "Revision:" in the controlfile seems to be ignored now; even Vim didn't syntax highlight it.

I tried putting it a version number like '1.2.3-mine1' in 'debian/changelog' and that worked. You get this warning[1], but it seems harmless. You can't use something like '+mine1' because that's considered part of the "upstream" release number, and so the tarball needs to have the same name.

[1] https://lintian.debian.org/tags/source-nmu-has-incorrect-version-number.html
debian  apt  packaging  packagemanagement  spec  guide  solution 
june 2016 by kme
Lintian Tag: source-nmu-has-incorrect-version-number
It's just a warning. It's what happens when you use something '2.2-mine1' in 'debian/changelog'.
debian  packaging  errormessage  solution 
june 2016 by kme
HowToPackageForDebian - Debian Wiki
For a Debian packaging tutorial:

- https://wiki.debian.org/BuildingAPackage

- also https://wiki.debian.org/Packaging/Intro

Prereqs:

sudo apt-get install build-essential dpatch fakeroot devscripts equivs lintian quilt
debian  packaging  packagemanagement  overview  reference 
june 2016 by kme
Packaging/Intro - Debian Wiki
See also: https://wiki.debian.org/BuildingAPackage

* Prerequisite packages:

$ sudo apt-get install build-essential dpatch fakeroot devscripts equivs lintian quilt

* Rename source package: mv hithere-1.0.tar.gz hithere_1.0.orig.tar.gz

* possibly just copy the 'debian' directory from the latest version available in the repositories; if not:

$ dch --create -v 1.0-1 --package hithere

* update 'debian/docs' if anything has changed in the source tarball (for example, tmux-2.2 removed the 'NOTES' file)

* within the unpacked source:

$ debuild -us -uc
debian  packaging  howto  packagemanagement  build  fromsource  toolchain  solution 
june 2016 by kme
BuildingAPackage - Debian Wiki
See also: https://wiki.debian.org/Packaging/Intro
sudo apt-get install build-essential dpatch fakeroot devscripts equivs lintian quilt
debian  packaging  gettingstarted  build  toolchain  packagemanagement  newbie  howto  solution 
june 2016 by kme
How to install new tmux 1.8 on Ubuntu 12.10 or 12.04? - Ask Ubuntu

12.04 AND UP:

sudo add-apt-repository ppa:pi-rho/dev
sudo apt-get update
sudo apt-get install tmux

OLD ANSWER:

As you possibly already realized, tmux version 1.8 is too new. As of writing this answer, version 1.8 is only 19 hours old.

There is indeed an official PPA for tmux, but don't expect new version to appear there instantly. It might take hours, days, and even weeks, and it's totally up to PPA maintainer.

If you for some reason need a newest version, then you might download the code and build/install tmux by yourself. Should not be a big deal, since tmux has dependencies only on libevent and ncurses packages, and both of these packages are present on most if not all of Linux distros. Just download the latest code, and type following via terminal:

$ sudo apt-get install libevent-dev libncurses-dev pkg-config
$ autoreconf -fis
$ ./configure
$ make
$ sudo make install
tmux  debian  ubuntu  build  fromsource  packaging  packagemanagement 
june 2016 by kme
Micropackages and Open Source Trust Scaling | Armin Ronacher's Thoughts and Writings
I think this pretty much nails the non-specific sense of dread that I have with using 'npm install <anything>'.
Any pin for anything other than a strict version match is a disaster waiting to happen if someone would manage to push out a point release for it by stealing juliangruber's credentials.
javascript  packaging  npm  opensource 
march 2016 by kme

Copy this bookmark:





to read