@menta: Updated the PKGBUILD now with your suggestions! Now just to check off the things that're still on my mental to-do list.
Search Criteria
Package Details: mikidown-git 0.3.11.r0.g87bdf2f-1
| Git Clone URL: | https://aur.archlinux.org/mikidown-git.git (read-only) |
|---|---|
| Package Base: | mikidown-git |
| Description: | A note taking application featuring markdown syntax |
| Upstream URL: | https://shadowkyogre.github.com/mikidown |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | rns |
| Maintainer: | ShadowKyogre |
| Last Packager: | ShadowKyogre |
| Votes: | 6 |
| Popularity: | 0.000000 |
| First Submitted: | 2012-07-22 15:02 |
| Last Updated: | 2016-08-15 18:20 |
Dependencies (10)
- python-markdown
- python-pyqt5 (python-pyqt5-hotfix)
- python-whoosh
- git (git-git) (make)
- aspell-en (optional) – pyenchant need backend support from aspell
- python-asciimathml (python-asciimathml-git) (optional) – for asciimath support
- python-html2text (python-html2text-git) (optional) – for converting to markdown (instead of HTML pasting)
- python-pyenchant (optional) – for spellchecking
- python-pygments (optional) – for code block syntax highlighting
- slickpicker (slickpicker-git) (optional) – for better color picking in mikidown for the highlighting color scheme
Required by (0)
Sources (1)
Latest Comments
ShadowKyogre commented on 2014-11-22 00:56
menta commented on 2014-11-15 11:46
@ShadowKyogre
Thank you for developing mikidown! I don't think you should append #develop to the sources, but I have some suggestions:
- Since rnons transferred the ownership of the project to you, you should be maintainer and rnons a contributor (https://wiki.archlinux.org/index.php/Arch_packaging_standards#AUR_packages).
- For the same reason I think _githubuser=ShadowKyogre will better reflect the current state. The sources URL works only since it redirects automatically.
- Since this is a development (git) package, I think the pkgver should reflect better this fact, so I suggest a slightly modified pkgver function.
- provides and conflicts fields can be useful to avoid package conflicts.
A modified PKGBUILD reflecting these suggestions is available at http://pastebin.com/ivNGZG13
menta commented on 2014-11-15 11:45
@ShadowKyogre
Thank you for developing mikidown! I don't think you should append #develop to the sources, but I have some suggestions:
- Since rnons transferred the ownership of the project to you, you should be maintainer and rnons a contributor (https://wiki.archlinux.org/index.php/Arch_packaging_standards#AUR_packages).
- For the same reason I think _githubuser=ShadowKyogre will better reflect the current state. The sources URL works only since it redirects autamatically.
- Since this is a development (git) package, I think the pkgver should reflect better this fact, so I suggest a slightly modified pkgver function.
- provides and conflicts fields can be useful to avoid package conflicts.
A modified PKGBUILD reflecting these suggestions is available at http://pastebin.com/ivNGZG13
ShadowKyogre commented on 2014-11-01 18:24
Updated the upstream URL accordingly after updating the package. Peculiarly, the sources URL still works even though we transferred ownership. Is anyone else experiencing that?
Other than that, does anyone else think I should append the #develop to the sources so this pulls the development version?
stoffl commented on 2014-07-19 07:35
Upstream URL gives 404, according to this pull request ownership of project has changed https://github.com/ShadowKyogre/mikidown/pull/33
new URL: https://github.com/ShadowKyogre/mikidown
rns commented on 2013-11-14 13:26
Sorry for the inconvenience, I forgot to update the setup.py file.
It should works now.
Nothing4You commented on 2013-11-14 12:06
==> Starting package()...
[...]
creating /home/rschwab/build/mikidown-git/pkg/mikidown-git/usr/share
creating /home/rschwab/build/mikidown-git/pkg/mikidown-git/usr/share/mikidown
copying README.mkd -> /home/rschwab/build/mikidown-git/pkg/mikidown-git/usr/share/mikidown
error: can't copy 'mikidown/notes.css': doesn't exist or not a regular file
==> ERROR: A failure occurred in package().
Aborting...
fluxboxer commented on 2013-11-04 08:51
All right, thank you.
rns commented on 2013-11-04 04:41
Oh, to build python-whoosh, you need to install python-setuptools first
# pacman -S python-setuptools
I will update PKGBUILD to make this explicit.
fluxboxer commented on 2013-11-02 20:58
Unfortunately:
Traceback (most recent call last):
File "setup.py", line 4, in <module>
from setuptools import setup, find_packages
ImportError: No module named 'setuptools'
==> ERROR: A failure occurred in package().
Aborting...
==> ERROR: Makepkg was unable to build python-whoosh.