Thanks for the explanation, Eli!
On Tue, Jan 3, 2017 at 11:36 PM, Eli Schwartz wrote:
> On 01/03/2017 04:12 PM, Leonid Bloch wrote:
> > Thanks! That was very helpful!
> >
> > All applied, except... "--skip-build" - indeed it makes sense, but I
> > have never seen it with other Python packages. S
On 01/03/2017 04:12 PM, Leonid Bloch wrote:
> Thanks! That was very helpful!
>
> All applied, except... "--skip-build" - indeed it makes sense, but I
> have never seen it with other Python packages. So I wonder if indeed it
> is a good practice, or is there some reason not to include it?
Well, py
Thanks! That was very helpful!
All applied, except... "--skip-build" - indeed it makes sense, but I have
never seen it with other Python packages. So I wonder if indeed it is a
good practice, or is there some reason not to include it?
Leonid.
On Tue, Jan 3, 2017 at 10:56 AM, Eli Schwartz via aur
On 01/03/2017 03:51 AM, Eli Schwartz wrote:
> and save on checking for updated source files in build().
Obviously, I meant to say "updated source files already checked in
build". :D
Specifically, not rerunning setuptools "build" ==> "build_py" in
package() and skipping straight to "install" ==> "
On 01/03/2017 03:14 AM, Leonid Bloch wrote:
> I'd like to put 3 new packages in the AUR. They are a part of one
> "kit", but are very different in functionality, therefore I think it
> will be better to introduce 3 packages, instead of one, which contains
> them all. You can see the details on: htt
You should never use git for downloading tagged releases. Copy the url of the
tar.gz from github and replace the version with pkgver. That way you can use
the sums (sha preferably).
Marcin Wieczorek wtorek, 03 stycznia 2017, 09:14AM +01:00 od Leonid Bloch
leonid.bl...@esrf.fr :
>Hi,
>
>I'd
