Hi,
It seems that it is reasonable to do so.
(Use +dfsg-1 first, then switch to +dfsgN-1)
Thanks!
2021年10月5日(火) 13:57 Russ Allbery :
>
> Kentaro Hayashi writes:
>
> > What do you think about it?
>
> > 1. We should use +dfsg-1 style
> > 2. We should use +dfsgN-1 style
> > 3. We should use
On Sat, 02 Oct 2021, Sean Whitton wrote:
> > When upstream codebase require repackaging for (only) other reasons than
> > DFSG compliance I instead use the hint "ds" (as in "derived source").
>
> Or "Debian source" :)
I always thought "ds" was for "debian specific" tarball. :-)
Cheers,
--
Quoting Russ Allbery (2021-10-05 06:57:00)
> Kentaro Hayashi writes:
>
> > What do you think about it?
>
> > 1. We should use +dfsg-1 style
> > 2. We should use +dfsgN-1 style
> > 3. We should use +dfsg.N-1 style
> > 4. Other
>
> I would start with +dfsg-1 because it's fairly rare to have to
Kentaro Hayashi writes:
> What do you think about it?
> 1. We should use +dfsg-1 style
> 2. We should use +dfsgN-1 style
> 3. We should use +dfsg.N-1 style
> 4. Other
I would start with +dfsg-1 because it's fairly rare to have to iterate on
the repackaging. You can then switch to +dfsgN-1
Hi,
Thank you for your explanation.
Very informative.
Reply in this thread talks about +/~, but
I'm curious about repacking count. (Subject may be misleading...)
What do you think about it?
1. We should use +dfsg-1 style
2. We should use +dfsgN-1 style
3. We should use +dfsg.N-1 style
4. Other
Quoting Sean Whitton (2021-10-02 22:32:18)
> On Sat 02 Oct 2021 at 03:03PM +02, Jonas Smedegaard wrote:
>
> > Quoting Kentaro Hayashi (2021-10-02 14:19:17)
> >> I want to know about the best practice of +dfsg and +ds extension.
> >> As far as I know, it is not well documented as a policy or
Hello,
On Sat 02 Oct 2021 at 03:03PM +02, Jonas Smedegaard wrote:
> Quoting Kentaro Hayashi (2021-10-02 14:19:17)
>> I want to know about the best practice of +dfsg and +ds extension.
>> As far as I know, it is not well documented as a policy or devref.
>
> When upstream codebase in its pristine
Jonas Smedegaard writes:
> I use ~ (tilde) as delimiter when possible, to make room for an eventual
> later release with the issues fixed, without needing ugly versioning or
> being forced to wait for a later upstream release.
The other advantage to using tilde is that if the repackaging to
On Sat, Oct 02, 2021 at 03:12:04PM +0200, Timo Röhling wrote:
> * Jonas Smedegaard [2021-10-02 15:03]:
> > I use ~ (tilde) as delimiter when possible, to make room for an eventual
> > later release with the issues fixed, without needing ugly versioning or
> > being forced to wait for a later
Quoting Timo Röhling (2021-10-02 15:12:04)
> * Jonas Smedegaard [2021-10-02 15:03]:
> >I use ~ (tilde) as delimiter when possible, to make room for an
> >eventual later release with the issues fixed, without needing ugly
> >versioning or being forced to wait for a later upstream release.
> Has
* Jonas Smedegaard [2021-10-02 15:03]:
I use ~ (tilde) as delimiter when possible, to make room for an eventual
later release with the issues fixed, without needing ugly versioning or
being forced to wait for a later upstream release.
Has this actually ever happened? I would expect that most
Quoting Kentaro Hayashi (2021-10-02 14:19:17)
> I want to know about the best practice of +dfsg and +ds extension.
> As far as I know, it is not well documented as a policy or devref.
When upstream codebase in its pristine form would violate the Debian
Free Software Guidelines (DFSG), I would
Hi,
I want to know about the best practice of +dfsg and +ds extension.
As far as I know, it is not well documented as a policy or devref.
In practical side of view, it seems that it varies on each maintainer.
Most well formalized document is "Choose a repack suffix" [2],
addtionally, mentors.d.n
13 matches
Mail list logo
