[aur-general] python2-crack question
Hello everyone, I have adopted my first package[1] on AUR (=D) and would like to know if is there a need to increase the "pkgrel" variable as I fixed a small error in the "build()" and "package()" functions. Also, I changed the sums to SHA256 instead of MD5. By the way, this package has the MIT/X license (python stuff) and I've seen on the PKGBUILD wiki [2] that, in this case, the license should be stored in /usr/share/licenses/pkg. But, would this be just copying it to the folder or what? Sincerely, [1] https://aur.archlinux.org/packages/python2-crack/ [2] https://wiki.archlinux.org/index.php/PKGBUILD#license *---* *Gabriel B. Casella* "Nothing is impossible, impossible just takes longer"
2013/5/10 Gabriel B. Casella <gbc921@gmail.com>
Hello everyone,
I have adopted my first package[1] on AUR (=D) and would like to know if is there a need to increase the "pkgrel" variable as I fixed a small error in the "build()" and "package()" functions. Also, I changed the sums to SHA256 instead of MD5.
By the way, this package has the MIT/X license (python stuff) and I've seen on the PKGBUILD wiki [2] that, in this case, the license should be stored in /usr/share/licenses/pkg. But, would this be just copying it to the folder or what?
Sincerely,
[1] https://aur.archlinux.org/packages/python2-crack/ [2] https://wiki.archlinux.org/index.php/PKGBUILD#license
*---* *Gabriel B. Casella* "Nothing is impossible, impossible just takes longer"
Hi Gabriel the package the license is include in readme and install files in this case need install two files install -Dm644 README ${pkgdir}/usr/share/licenses/${pkgname}/README install -Dm644 INSTALL ${pkgdir}/usr/share/licenses/${pkgname}/INSTALL or extract that licenses fron that files and put on in License1 and License2 (or both in same file) and install in the same metod i've download your package, and namcap say this: python2-crack E: ELF file ('usr/lib/python2.7/site-packages/_crack.so') found in an 'any' package. in this case need add arch=('x86_64' 'i686') instead arch=('any') and python2-crack E: Dependency python detected and not included (programs ['python'] needed in scripts ['usr/share/doc/python-crack/checkpass.py']) this need more package workground, for example "sed" all .py script to change python to python2 (if you want only python2 package) like: find -type f -name '*.py*' -exec sed -i 's|/usr/bin/python$|&2|g' {} \; note: the patch is in prepare() function, not in build() greetings
Thanks man! I've implemented and everything works fine! (though namcap still complains about the license) Should I increase the "pkgrel" or is not the case? If you can take a look at the PKGBUILD again just to make sure that prepare() and build() have the commands at the right place, I would appreciate. --- BTW, I could not fully understand the sed command. I know (or I suppose) that is looking for anything with /usr/bin/python$ and inserting two at the end. But, why the "s pipe" at the beggining and "pipe g" at the end? Also, why having "{} \;" at the end? Is it the termination condition of the sed/exec? PS.: I'm not English native too, so don't worry. *---* *Gabriel B. Casella* "Nothing is impossible, impossible just takes longer" On Fri, May 10, 2013 at 12:11 AM, SpinFlo <sl1pkn07@gmail.com> wrote:
2013/5/10 SpinFlo <sl1pkn07@gmail.com>
blablabla
And sorry my typos and "english" XD
----------------------------------------
From: gbc921@gmail.com Date: Mon, 13 May 2013 10:33:03 -0300 To: aur-general@archlinux.org Subject: Re: [aur-general] python2-crack question
Thanks man!
I've implemented and everything works fine! (though namcap still complains about the license)
Should I increase the "pkgrel" or is not the case?
If the resulting package is different, either the pkgver or the pkgrel should change
If you can take a look at the PKGBUILD again just to make sure that prepare() and build() have the commands at the right place, I would appreciate.
You want to the configure command in the build function. Other than that, you're fine with command locations. You should put quotes around any variables that could expand to include spaces ($pkgdir and $srcdir especially).
--- BTW, I could not fully understand the sed command.
I know (or I suppose) that is looking for anything with /usr/bin/python$ and inserting two at the end. But, why the "s pipe" at the beggining and "pipe g" at the end? Also, why having "{} \;" at the end? Is it the termination condition of the sed/exec?
Those aren't "pipes", they're separators for the sed command. Read up on the sed command http://www.gnu.org/software/sed/manual/sed.html, especially section 3.5. When using find, {} stand for the found file, and \; terminates the -exec part of the find command.
PS.: I'm not English native too, so don't worry.
*---* *Gabriel B. Casella* "Nothing is impossible, impossible just takes longer"
On Fri, May 10, 2013 at 12:11 AM, SpinFlo <sl1pkn07@gmail.com> wrote:
2013/5/10 SpinFlo <sl1pkn07@gmail.com>
blablabla
And sorry my typos and "english" XD
Thanks. I changed the quotes and increased pkgrel, so other arch users can receive the update. This online sed manual has more explanation than the man page. Now I get it. Sincerely, *---* *Gabriel B. Casella* "Nothing is impossible, impossible just takes longer" On Mon, May 13, 2013 at 10:46 AM, Doug Newgard <scimmia22@outlook.com>wrote:
----------------------------------------
From: gbc921@gmail.com Date: Mon, 13 May 2013 10:33:03 -0300 To: aur-general@archlinux.org Subject: Re: [aur-general] python2-crack question
Thanks man!
I've implemented and everything works fine! (though namcap still complains about the license)
Should I increase the "pkgrel" or is not the case?
If the resulting package is different, either the pkgver or the pkgrel should change
If you can take a look at the PKGBUILD again just to make sure that prepare() and build() have the commands at the right place, I would appreciate.
You want to the configure command in the build function. Other than that, you're fine with command locations. You should put quotes around any variables that could expand to include spaces ($pkgdir and $srcdir especially).
--- BTW, I could not fully understand the sed command.
I know (or I suppose) that is looking for anything with /usr/bin/python$ and inserting two at the end. But, why the "s pipe" at the beggining and "pipe g" at the end? Also, why having "{} \;" at the end? Is it the termination condition of
the
sed/exec?
Those aren't "pipes", they're separators for the sed command. Read up on the sed command http://www.gnu.org/software/sed/manual/sed.html, especially section 3.5. When using find, {} stand for the found file, and \; terminates the -exec part of the find command.
PS.: I'm not English native too, so don't worry.
*---* *Gabriel B. Casella* "Nothing is impossible, impossible just takes longer"
On Fri, May 10, 2013 at 12:11 AM, SpinFlo <sl1pkn07@gmail.com> wrote:
2013/5/10 SpinFlo <sl1pkn07@gmail.com>
blablabla
And sorry my typos and "english" XD
participants (3)
-
Doug Newgard
-
Gabriel B. Casella
-
SpinFlo