On Fri, Dec 9, 2016, at 01:42 PM, Ihar Hrachyshka wrote:
> Ihar Hrachyshka wrote:
>
> > Jeremy Stanley wrote:
> >
> >> On 2016-10-04 18:22:10 +0200 (+0200), Ihar Hrachyshka wrote:
> >> [...]
> >>> When I execute 'bindep test’ locally, I get the following error on
> >>> centos7.2
> >>> which is
Ihar Hrachyshka wrote:
Jeremy Stanley wrote:
On 2016-10-04 18:22:10 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
When I execute 'bindep test’ locally, I get the following error on
centos7.2
which is expected:
Bad versions of installed packages:
sqlite version 3.7.17-8.el7 does not mat
Jeremy Stanley wrote:
On 2016-10-04 18:22:10 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
When I execute 'bindep test’ locally, I get the following error on
centos7.2
which is expected:
Bad versions of installed packages:
sqlite version 3.7.17-8.el7 does not match >=3.8
I would think th
On 2016-10-04 18:22:10 +0200 (+0200), Ihar Hrachyshka wrote:
[...]
> When I execute 'bindep test’ locally, I get the following error on centos7.2
> which is expected:
>
> Bad versions of installed packages:
> sqlite version 3.7.17-8.el7 does not match >=3.8
>
> I would think that this output
Andreas Jaeger wrote:
TL;DR: Projects can use bindep.txt to document in a programmatic way
their binary dependencies
Python developers record their dependencies on other Python packages in
requirements.txt and test-requirements.txt. But some packages
havedependencies outside of python and we s
On 2016-08-17 09:21:49 -0700 (-0700), John Villalovos wrote:
> Maybe I missed it, but it would be nice if the documentation had some
> sample commented bindep.txt files.
Seems like a grand idea. I'll start a change to add a section to the
bindep documentation.
--
Jeremy Stanley
_
On Fri, Aug 12, 2016 at 10:31 AM, Andreas Jaeger wrote:
> TL;DR: Projects can use bindep.txt to document in a programmatic way
> their binary dependencies
>
>
Maybe I missed it, but it would be nice if the documentation had some
sample commented bindep.txt files.
Thanks,
John
___
On 2016-08-16 18:15:53 -0500 (-0500), Matthew Thode wrote:
> I look at it (as a packager), though it is somewhat dubious as to
> whether or not what's there is actually needed. Having test-bindep.txt
> like we have test-requirements would be helpful.
In my mind, our use of bindep.txt is mostly in
On 2016-08-16 17:38:32 -0500 (-0500), Brant Knudson wrote:
> Is bindep.txt meant to be used by anything other than OpenStack
> CI? (As in, are packagers going to rely on it?)
It's meant first and foremost to be used as documentation for
developers but formatted in a machine-parseable way so that w
On 08/16/2016 05:38 PM, Brant Knudson wrote:
> s bindep.txt meant to be used by anything other than OpenStack CI? (As
> in, are packagers going to rely on it?)
>
> In keystone's bindep.txt, we have packages listed like:
>
> |libldap2-dev [platform:dpkg] |
>
>
> -> Which is only needed if you in
On Fri, Aug 12, 2016 at 2:53 PM, Jeremy Stanley wrote:
> On 2016-08-12 21:20:34 +0200 (+0200), Julien Danjou wrote:
> [...]
> > If bindep.txt is present, are the "standard" packages still installed?
> > If yes, this is going to be more challenging to get bindep.txt right, as
> > a missing entry w
On 2016-08-12 21:20:34 +0200 (+0200), Julien Danjou wrote:
[...]
> If bindep.txt is present, are the "standard" packages still installed?
> If yes, this is going to be more challenging to get bindep.txt right, as
> a missing entry will go unnoticed.
As Andreas mentioned, we have a fallback list[*]
On 08/12/2016 09:20 PM, Julien Danjou wrote:
> On Fri, Aug 12 2016, Andreas Jaeger wrote:
>
>> Projects are encouraged to create their own bindep files. Besides
>> documenting what is required, it also gives a speedup in running tests
>> since you install only what you need and not all packages th
On 12 August 2016 at 12:09, Clay Gerrard wrote:
>
>
> On Fri, Aug 12, 2016 at 11:52 AM, Andreas Jaeger wrote:
>>
>> On 08/12/2016 08:37 PM, Clay Gerrard wrote:
>> >
>> > ... but ... it doesn't have a --install option? Do you know if that is
>> > strictly out-of-scope or roadmap or ... ?
>>
>>
>>
On Fri, Aug 12 2016, Andreas Jaeger wrote:
> Projects are encouraged to create their own bindep files. Besides
> documenting what is required, it also gives a speedup in running tests
> since you install only what you need and not all packages that some
> other project might need and are installed
On Fri, Aug 12, 2016 at 11:52 AM, Andreas Jaeger wrote:
>
> On 08/12/2016 08:37 PM, Clay Gerrard wrote:
> >
> > ... but ... it doesn't have a --install option? Do you know if that is
> > strictly out-of-scope or roadmap or ... ?
>
>
> Right now we don't need it - we take the output and pipe that
On 08/12/2016 08:37 PM, Clay Gerrard wrote:
> I'd noticed other-requirements.txt around, but figured it needed a bunch
> of custom tooling to actually make it useful.
>
> And... it's a subprocess wrapper to a handful of package management
> tools (surprised to see emerge and pacmac - Kudos!) and a
On 08/12/2016 08:07 PM, John Dickinson wrote:
> bindep is great, and we've been using it in Swift for a while now. I'd
> definitely recommend it to other projects.
>
> Andreas, I didn't see a patch proposed to Swift to move the file. I don't
> want to get in the way of your tool, though. Is ther
I'd noticed other-requirements.txt around, but figured it needed a bunch of
custom tooling to actually make it useful.
And... it's a subprocess wrapper to a handful of package management tools
(surprised to see emerge and pacmac - Kudos!) and a custom format for
describing package requirements...
bindep is great, and we've been using it in Swift for a while now. I'd
definitely recommend it to other projects.
Andreas, I didn't see a patch proposed to Swift to move the file. I don't want
to get in the way of your tool, though. Is there a patch that will be proposed,
or should I do that my
TL;DR: Projects can use bindep.txt to document in a programmatic way
their binary dependencies
Python developers record their dependencies on other Python packages in
requirements.txt and test-requirements.txt. But some packages
havedependencies outside of python and we should document
thesedepend
21 matches
Mail list logo
