ebfe commented on this pull request.
> @@ -1227,6 +1228,16 @@ The following variables influence how Haskell packages are built:
- `make_build_args`: This is passed as-is to `stack build ...`, so
you can add your `--flag ...` parameters there.
+<a id="pkgs_transitional"></a>
+### Transitional packages
+
+Transitional packages are used to move users into a new package. It is commonly
+used when upstream changes it's name and Void Linux changes the package name to
+reflect such change. A transitive package must be an empty subpackage of the
s/transitive/transitional/
ebfe commented on this pull request.
> @@ -1227,6 +1228,16 @@ The following variables influence how Haskell packages are built:
- `make_build_args`: This is passed as-is to `stack build ...`, so
you can add your `--flag ...` parameters there.
+<a id="pkgs_transitional"></a>
+### Transitional packages
+
+Transitional packages are used to move users into a new package. It is commonly
+used when upstream changes it's name and Void Linux changes the package name to
+reflect such change. A transitive package must be an empty subpackage of the
+package of the new main package, on the subpackage, it must have `noarch=yes`,
+`short_desc+"= - transitional package"` and
+`depends="${pkgname}-${version}_${revision}"`
s/pkgname/sourcepkg/
Thanks for catching, will fix when I get home in about 1 hour
On Fri, Mar 30, 2018, 08:46 Michael Gehring <notifications@github.com>
wrote:
> *@ebfe* commented on this pull request.
> ------------------------------
>
> In Manual.md
> <https://github.com/voidlinux/void-packages/pull/13064#discussion_r178277=
684>
> :
>
> > @@ -1227,6 +1228,16 @@ The following variables influence how Haskell pa=
ckages are built:
> - `make_build_args`: This is passed as-is to `stack build ...`, so
> you can add your `--flag ...` parameters there.
>
> +<a id=3D"pkgs_transitional"></a>
> +### Transitional packages
> +
> +Transitional packages are used to move users into a new package. It is c=
ommonly
> +used when upstream changes it's name and Void Linux changes the package =
name to
> +reflect such change. A transitive package must be an empty subpackage of=
the
>
> s/transitive/transitional/
>
> =E2=80=94
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/voidlinux/void-packages/pull/13064#pullrequestreview-=
108315846>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AdUHTfOZJGEwYbn14JLj32=
V-Mg5PzemWks5tjhr3gaJpZM4TBhdw>
> .
>
--=20
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/voidlinux/void-packages/pull/13064#issuecomment-377508300=
Will fix whenever I get home eta 1h
On Fri, Mar 30, 2018, 08:46 Michael Gehring <notifications@github.com>
wrote:
> *@ebfe* commented on this pull request.
> ------------------------------
>
> In Manual.md
> <https://github.com/voidlinux/void-packages/pull/13064#discussion_r178277=
728>
> :
>
> > @@ -1227,6 +1228,16 @@ The following variables influence how Haskell pa=
ckages are built:
> - `make_build_args`: This is passed as-is to `stack build ...`, so
> you can add your `--flag ...` parameters there.
>
> +<a id=3D"pkgs_transitional"></a>
> +### Transitional packages
> +
> +Transitional packages are used to move users into a new package. It is c=
ommonly
> +used when upstream changes it's name and Void Linux changes the package =
name to
> +reflect such change. A transitive package must be an empty subpackage of=
the
> +package of the new main package, on the subpackage, it must have `noarch=
=3Dyes`,
> +`short_desc+"=3D - transitional package"` and
> +`depends=3D"${pkgname}-${version}_${revision}"`
>
> s/pkgname/sourcepkg/
>
> =E2=80=94
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/voidlinux/void-packages/pull/13064#pullrequestreview-=
108315906>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AdUHTd-3SL40twkza1j6kx=
hJCxjE5j90ks5tjhsRgaJpZM4TBhdw>
> .
>
--=20
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/voidlinux/void-packages/pull/13064#issuecomment-377508403=
Maybe it would be good to indentify/explain why these are needed at all. Why doesn't replaces=(/provides=) work? Also see #11804.
These transitional packages have the problem that you never know when they can be safely removed, so i'm not sure if they should be encouraged.
newbluemoon commented on this pull request.
> @@ -1227,6 +1228,16 @@ The following variables influence how Haskell pa=
ckages are built:
- `make_build_args`: This is passed as-is to `stack build ...`, so
you can add your `--flag ...` parameters there.
=
+<a id=3D"pkgs_transitional"></a>
+### Transitional packages
+
+Transitional packages are used to move users into a new package. It is c=
ommonly
+used when upstream changes it's name and Void Linux changes the package =
name to
I think it must be =E2=80=9Cits name=E2=80=9D.
-- =
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/voidlinux/void-packages/pull/13064#pullrequestreview-1=
08316626=
As far as I can tell replaces provides doesn't update people with the old
package
On Fri, Mar 30, 2018, 08:51 Michael Gehring <notifications@github.com>
wrote:
> Maybe it would be good to indentify/explain why these are needed at all.
> Why doesn't replaces=3D(/provides=3D) work? Also see #11804
> <https://github.com/voidlinux/void-packages/issues/11804>.
>
> These transitional packages have the problem that you never know when they
> can be safely removed, so i'm not sure if they should be encouraged.
>
> =E2=80=94
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/voidlinux/void-packages/pull/13064#issuecomment-37750=
8940>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AdUHTcCuCrGQuVLpSK0IJ9=
n25Y08kZV-ks5tjhxQgaJpZM4TBhdw>
> .
>
--=20
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/voidlinux/void-packages/pull/13064#issuecomment-377509371=
newbluemoon commented on this pull request.
> @@ -1227,6 +1228,16 @@ The following variables influence how Haskell pa=
ckages are built:
- `make_build_args`: This is passed as-is to `stack build ...`, so
you can add your `--flag ...` parameters there.
=
+<a id=3D"pkgs_transitional"></a>
+### Transitional packages
+
+Transitional packages are used to move users into a new package. It is c=
ommonly
+used when upstream changes it's name and Void Linux changes the package =
name to
+reflect such change. A transitive package must be an empty subpackage of=
the
+package of the new main package, on the subpackage, it must have `noarch=
=3Dyes`, =
Is there a =E2=80=9Cpackage=E2=80=9D too much? And maybe split into two s=
entences for better readability?
-- =
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/voidlinux/void-packages/pull/13064#pullrequestreview-1=
08317289=
> As far as I can tell replaces provides doesn't update people with the old package
But that's exactly what replaces is for. replaces=oldname>=0 and revbumping all revdeps so they refer to the new name should take care of that. As far as i understand it the only reason to use transitional packages is to avoid the revbump of the revdeps. But all in all replaces should be the "default" rename strategy as it also takes care of removing the old package from the system and doesn't clobber the repo with dummy packages.
> If nothing pulls in a package into the transaction it would never be considered for replaces=.
If that's the case then maybe that should be fixed instead of adding transitional packages.
> > If nothing pulls in a package into the transaction it would never be considered for replaces=.
>
> If that's the case then maybe that should be fixed instead of adding transitional packages.
Which of course isn't trivial to do since it's used in combination with
provides for virtual packages which relies on this
behaviour. And is at the same time broken by it ((releated bug
https://github.com/voidlinux/xbps/issues/257). Which leads us back to #11804.
pullmoll commented on this pull request.
> @@ -1227,6 +1228,16 @@ The following variables influence how Haskell packages are built:
- `make_build_args`: This is passed as-is to `stack build ...`, so
you can add your `--flag ...` parameters there.
+<a id="pkgs_transitional"></a>
+### Transitional packages
+
+Transitional packages are used to move users into a new package. It is commonly
+used when upstream changes it's name and Void Linux changes the name to reflect
s/it's/its/
maxice8 commented on this pull request.
> @@ -1227,6 +1228,16 @@ The following variables influence how Haskell packages are built:
- `make_build_args`: This is passed as-is to `stack build ...`, so
you can add your `--flag ...` parameters there.
+<a id="pkgs_transitional"></a>
+### Transitional packages
+
+Transitional packages are used to move users into a new package. It is commonly
+used when upstream changes it's name and Void Linux changes the name to reflect
fixed,, thanks
soooo, what is the current plan ? document replaces= / provides= and make Transitional packages documentation just explain how to use those to make a transitional package ?
I think it became clear that renaming packages isn't a 'triviality' so I propose:
```markdown
# Renaming packages
Don't do it unless you know what you are doing.
```
until replaces/provides semantics are clear and implemented in a sane way in xbps. (only half joking)