Le jeudi 26 juillet 2018 à 21:01 +0900, Jens-Ulrik Petersen a écrit :
> On Thu, Jul 26, 2018 at 7:10 PM Nicolas Mailhot <
>
> > To be complete it should also be boostrap-aware : do intermediary
> > bootsrap builds whenever there is a cycle and one or more links in
> > the
> > cycle have
On Fri, Jul 27, 2018 at 1:21 PM Michal Novotny wrote:
> On Fri, Jul 27, 2018 at 4:56 AM Jens-Ulrik Petersen
> wrote:
>
>> On Fri, Jul 27, 2018 at 12:54 AM Jens-Ulrik Petersen
>> wrote:
>>
>>> I should test some larger package sets to see how well rpmbuild-order
>>> scales too...
>>>
>>
>> BTW
On 07/26/2018 11:52 AM, Igor Gnatenko wrote:
>>> Note that mizdebsk already had such tool for quite some time.
>>>
>>
>> Do you have a reference?
>>
>
> CCing Mikolaj.
Latest version of the code Igor is talking about is available at [1].
The tool is targeted for solving specific problem -
Hello,
On Fri, Jul 27, 2018 at 4:56 AM Jens-Ulrik Petersen
wrote:
> On Fri, Jul 27, 2018 at 12:54 AM Jens-Ulrik Petersen
> wrote:
>
>> I should test some larger package sets to see how well rpmbuild-order
>> scales too...
>>
>
> BTW are there any tarballs of all the fedora spec files available
On Fri, Jul 27, 2018 at 12:54 AM Jens-Ulrik Petersen
wrote:
> I should test some larger package sets to see how well rpmbuild-order
> scales too...
>
BTW are there any tarballs of all the fedora spec files available somewhere
these days?
Of course I could download srpms, or better: script
You are absolutely correct: there are times, e.g., that drinking coffee is
"more important" to me than say, replying to e-mail. However I don't think that
Haskel is the best language to feature up an already existing uglix tool.
Meanwhile I do not know of a tool that schedules rpm builds
On Thu, 2018-07-26 at 15:40 +, Jeff Johnson wrote:
> There are easier ways to accomplish build ordering using tsort(1) and a minor
> amount of scripting with the same simplifying assumptions your program is
> making:
> 1) no cycles
> 2) every package provides its own name
> 3) every package
On Thu, Jul 26, 2018 at 6:04 PM Jens-Ulrik Petersen
wrote:
> On Fri, Jul 27, 2018 at 12:42 AM Jeff Johnson wrote:
>
>> There are easier ways to accomplish build ordering using tsort(1) and a
>> minor amount of scripting with the same simplifying assumptions your
>> program is making:
>> 1) no
On Fri, Jul 27, 2018 at 12:42 AM Jeff Johnson wrote:
> There are easier ways to accomplish build ordering using tsort(1) and a
> minor amount of scripting with the same simplifying assumptions your
> program is making:
> 1) no cycles
> 2) every package provides its own name
> 3) every package
There are easier ways to accomplish build ordering using tsort(1) and a minor
amount of scripting with the same simplifying assumptions your program is
making:
1) no cycles
2) every package provides its own name
3) every package supplies prerequisite package names without versions
tsort(1) just
On Thu, Jul 26, 2018 at 7:10 PM Nicolas Mailhot
wrote:
> Le 2018-07-26 07:20, Jens-Ulrik Petersen a écrit :
> > https://github.com/juhp/rpmbuild-order
> > It works by reading the BRs in spec files of the packages you want to
> > build, generating a graph of their interdependencies internally,
On Thu, Jul 26, 2018 at 6:53 PM Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:
> On Thu, Jul 26, 2018 at 11:44 AM Jens-Ulrik Petersen
> wrote:
>
>> On Thu, Jul 26, 2018 at 2:44 PM Igor Gnatenko <
>> ignatenkobr...@fedoraproject.org> wrote:
>>
>>> So… Since I have hard times
On Thu, Jul 26, 2018 at 3:58 PM David Tardon wrote:
> On Thu, 2018-07-26 at 14:20 +0900, Jens-Ulrik Petersen wrote:
> > You can try it from my copr repo:
> > https://copr.fedorainfracloud.org/coprs/petersen/rpmbuild-order
>
> - nothing provides
>
Le 2018-07-26 07:20, Jens-Ulrik Petersen a écrit :
Hi
https://github.com/juhp/rpmbuild-order
It works by reading the BRs in spec files of the packages you want to
build, generating a graph of their interdependencies internally, from
which it outputs the packages in a build dependency order. If
On Thu, Jul 26, 2018 at 11:44 AM Jens-Ulrik Petersen
wrote:
> On Thu, Jul 26, 2018 at 2:44 PM Igor Gnatenko <
> ignatenkobr...@fedoraproject.org> wrote:
>
>> So… Since I have hard times understanding code, I will just ask questions
>> here:
>> * Does it use libsolv? I guess not.
>> * Does it
On Thu, Jul 26, 2018 at 2:44 PM Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:
> So… Since I have hard times understanding code, I will just ask questions
> here:
> * Does it use libsolv? I guess not.
> * Does it handle rich dependencies? I guess not.
>
It only uses BuildRequires
On Thu, Jul 26, 2018 at 1:21 PM Jens-Ulrik Petersen wrote:
>
> Hi,
>
> This is an early announcement about a tool called 'rpmbuild-order' I made to
> sort RPM-based packages in build dependency order. I am not sure if such a
> tool exists already? Certainly some tools like `mockchain` can
On Thu, 2018-07-26 at 14:20 +0900, Jens-Ulrik Petersen wrote:
> You can try it from my copr repo:
> https://copr.fedorainfracloud.org/coprs/petersen/rpmbuild-order
Error:
Problem: conflicting requests
- nothing provides
On Thu, Jul 26, 2018 at 7:29 AM Jens-Ulrik Petersen
wrote:
> Hi,
>
> This is an early announcement about a tool called 'rpmbuild-order' I made
> to sort RPM-based packages in build dependency order. I am not sure if such
> a tool exists already? Certainly some tools like `mockchain` can already
Hi,
This is an early announcement about a tool called 'rpmbuild-order' I made
to sort RPM-based packages in build dependency order. I am not sure if such
a tool exists already? Certainly some tools like `mockchain` can already
order builds in this way, but I don't know of such a standalone
20 matches
Mail list logo
