[kdesrc-build] [Bug 354796] Add no-src configuration option, similar to the command line option

2024-05-10 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=354796

Andrew Shark  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/
   |kdesrc-build/-/commit/d8104 |kdesrc-build/-/commit/68dbc
   |fa8e9defa5b25f7eab538a7b0f2 |8f847165e08fcd7559df8eefd79
   |fc652e1d|71d8a68b

--- Comment #10 from Andrew Shark  ---
Git commit 68dbc8f847165e08fcd7559df8eefd7971d8a68b by Andrew Shark.
Committed on 28/01/2024 at 21:24.
Pushed by ashark into branch 'docbook_historied_per_file'.

Support phase selection individually for modules and module-sets

Previously we could only select phases globally from command line. They were
applied to all modules.

Sometimes user want to control phase selection for individual module.

The clone is happening from the remote/origin by default. This becomes a
problem when user is working with a local branch that is not presented in
remote. For example, user may not have a developer account, or just does not
want to upload his work even in work/user branch yet.

He just wants kdesrc-build to not touch the sources of that module (while the
other modules still be updated), and does not want to exclude module from build
phase.

Let's say user wants to work with `kio`, and testing it with `ark`.
Previously, user could achieve this task by running `kdesrc-build` several
times. Different quirks were needed. Example:
- `kdesrc-build ark --include-dependencies` - build ark with dependencies
(including kio) as normal
- `...` - make changes to the kio project
- `kdesrc-build kio --no-src --no-include-dependencies`
- `kdesrc-build ark --include-dependencies --ignore-modules kio`

After this commit user can specify the `no-src` option for the `kio` module,
and then just run `kdesrc-build ark --include-dependencies`. The `kio` will not
be updated in this process, but will not be excluded from build phase.

Original commit: d8104fa8
https://invent.kde.org/sdk/kdesrc-build/-/commit/d8104fa8e9defa5b25f7eab538a7b0f2fc652e1d

M  +88   -14   doc/kdesrc-buildrc/conf-options-table.docbook

https://invent.kde.org/sdk/kdesrc-build/-/commit/68dbc8f847165e08fcd7559df8eefd7971d8a68b

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdesrc-build] [Bug 354796] Add no-src configuration option, similar to the command line option

2024-01-28 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=354796

Andrew Shark  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/sdk/
   ||kdesrc-build/-/commit/d8104
   ||fa8e9defa5b25f7eab538a7b0f2
   ||fc652e1d
 Status|CONFIRMED   |RESOLVED

--- Comment #9 from Andrew Shark  ---
Git commit d8104fa8e9defa5b25f7eab538a7b0f2fc652e1d by Andrew Shark.
Committed on 28/01/2024 at 21:24.
Pushed by ashark into branch 'master'.

Support phase selection individually for modules and module-sets

Previously we could only select phases globally from command line. They were
applied to all modules.

Sometimes user want to control phase selection for individual module.

The clone is happening from the remote/origin by default. This becomes a
problem when user is working with a local branch that is not presented in
remote. For example, user may not have a developer account, or just does not
want to upload his work even in work/user branch yet.

He just wants kdesrc-build to not touch the sources of that module (while the
other modules still be updated), and does not want to exclude module from build
phase.

Let's say user wants to work with `kio`, and testing it with `ark`.
Previously, user could achieve this task by running `kdesrc-build` several
times. Different quirks were needed. Example:
- `kdesrc-build ark --include-dependencies` - build ark with dependencies
(including kio) as normal
- `...` - make changes to the kio project
- `kdesrc-build kio --no-src --no-include-dependencies`
- `kdesrc-build ark --include-dependencies --ignore-modules kio`

After this commit user can specify the `no-src` option for the `kio` module,
and then just run `kdesrc-build ark --include-dependencies`. The `kio` will not
be updated in this process, but will not be excluded from build phase.

M  +88   -14   doc/conf-options-table.docbook
M  +2-1modules/ksb/Application.pm
M  +0-1modules/ksb/BuildContext.pm
M  +13   -9modules/ksb/Cmdline.pm
M  +47   -1modules/ksb/Module.pm

https://invent.kde.org/sdk/kdesrc-build/-/commit/d8104fa8e9defa5b25f7eab538a7b0f2fc652e1d

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdesrc-build] [Bug 354796] Add no-src configuration option, similar to the command line option

2023-09-07 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=354796

--- Comment #8 from Andrew Shark  ---
The [documentation for conf
options](https://docs.kde.org/trunk5/en/kdesrc-build/kdesrc-build/conf-options-table.html)
actually lists:
```
no-svn  Module setting overrides global If this option is set to true then
kdesrc-build will not update the source code for the module automatically. It
will still try to build the module if it normally would have tried anyways.
```

According to [documentation for command line
options](https://docs.kde.org/trunk5/en/kdesrc-build/kdesrc-build/supported-cmdline-params.html),
the `--no-svn` is an equivalent to the `--no-svn`.

I tried the following in the config:
```
options kio
no-src true
end options
```
and also:
```
options kio
 no-svn true
end options
```
Unfortunately, this is completely ignored in both cases.

The build process switches branch to master every time it is built. (I am
building ark, and kio is its dependency). But if I specify `branch` with my
local branch name, it will fail, because it tries to download that from remote
(that does not exist).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdesrc-build] [Bug 354796] Add no-src configuration option, similar to the command line option

2023-09-01 Thread Andrew Shark
https://bugs.kde.org/show_bug.cgi?id=354796

Andrew Shark  changed:

   What|Removed |Added

Summary|kdesrc-build ignores no-src |Add no-src configuration
   |module option   |option, similar to the
   ||command line option
 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
 CC||ash...@linuxcomp.ru

--- Comment #7 from Andrew Shark  ---
This is accurate. Currently, the no-src option is not supported in
configuration, see
https://docs.kde.org/trunk5/en/kdesrc-build/kdesrc-build/conf-options-table.html

-- 
You are receiving this mail because:
You are watching all bug changes.