Re: Best approach for packaging new major version of package that contains version
2022, ജൂലൈ 4 8:49:00 PM IST, Mathias Gibbens <mathias@calenhad.com>ൽ എഴുതി
>On Sun, 2022-07-03 at 11:30 +0530, Nilesh Patra wrote:
>> On 7/2/22 12:11 PM, Shengjing Zhu wrote:
>> > On Sat, Jul 2, 2022 at 10:56 AM Nilesh Patra
>> > <nilesh@nileshpatra.info> wrote:
>> > >
>> > > On 7/2/22 1:46 AM, Mathias Gibbens wrote:
>> > > > I am going to need to package version 3.0.0 of golang-
>> > > > gopkg-macaroon-
>> > > > bakery, as the [...] However, the current package in Debian for
>> > > > this library
>> > > > is named "golang-gopkg-macaroon-bakery.v2" [...]
>> > >
>> > > > the group consensus is for the preferred
>> > > > name for the new package: "golang-gopkg-macaroon-bakery.v3" or
>> > > > just
>> > > > plain "golang-gopkg-macaroon-bakery".
>> > >
>> > > golang-gopkg-macaroon-bakery.v3
>> > >
>> >
>> > Neither is not right. As the import path is
>> > github.com/go-macaroon-bakery/macaroon-bakery/v3.
>> > Not gopkg.io/macaroon-bakery.v2.
>>
>> Oops, I was somehow careless when I copy-pasted this.
>> Thanks for watching me
>>
>
> ACK, thanks for your guidance. I'll go with the source package name
>golang-github-go-macaroon-bakery-macaroon-bakery.
I think source package not including the version helps in keeping a single repo instead of creating new repos for every version. Binary package can be bumped to avoid breakages.
>Mathias
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply to: