[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A side note on depricated components vs packagage possibilties (debian)
[Thread Prev] | [Thread Next]
- Subject: Re: A side note on depricated components vs packagage possibilties (debian)
- From: gbWilly <gbWilly@xxxxxxxxxxxxxx>
- Date: Wed, 04 Dec 2024 16:57:37 +0000
- To: BB <adamnt42@xxxxxxxxx>
- Cc: user@xxxxxxxxxxxxxxxxxxxxxx
On Wednesday, December 4th, 2024 at 04:08, BB <adamnt42@xxxxxxxxx> wrote: > On 4/12/24 7:55 am, gbWilly wrote: > > > So the question is, are there components that can replace existing onces, without breaking older code? > > > No that is not the question. > > The question is, when I am using a locally modified gb.db (in > particular, gb.db.postgresql) and have been doing so for 12 years, how > upset am I going to be when this "replacing" happens! > > b Valid point there Bruce, but easily solved. You rename your custom gb.db.postgresql component to another name and let your projects depend on that. No upstream change will then mess up your projects. gbWilly
A side note on depricated components vs packagage possibilties (debian) | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
Re: A side note on depricated components vs packagage possibilties (debian) | BB <adamnt42@xxxxxxxxx> |