creating private versions of public packages with changes (naming & versioning issue)

Marius Gedminas marius at pov.lt
Tue Oct 22 05:11:46 UTC 2013


On Mon, Oct 21, 2013 at 02:28:36PM -0700, Michael Barrett wrote:
> Thanks - yeah, I haven't seen anything online or in the packaging manual
> that suggests how this should be handled.  I liked your idea of using the
> epoch - but then I saw this:
> 
> 
> # dpkg -l | awk '{print $3}' | grep ":" | wc -l
> 132
> 
> That's on my vagrant ubuntu 12.04 box, so it seems like epoch is used by
> quite a few packages (like 10% of the installed packages on my VM).
> 
> Anyone else have any ideas?

apt pinning, perhaps?

http://manpages.ubuntu.com/manpages/precise/man5/apt_preferences.5.html

Personally I append 'mg1' etc. to the original version (so I end up with
e.g. 1.2.3-5ubuntu3mg1), and then whenever a new package update appears,
I'll know that I need to update my patched one.

Then again whenever I build patched packages, it's to get backports of
bugfixes that will eventually make their way upstream, so it's a
strictly temporary thing.

Marius Gedminas
-- 
Ways in which you can avoid starting a flame war on a Debian mailing list.
The subtle:

 * Write in your TODO list that you definitely need to reply to that mail

        -- Enrico Zini
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20131022/6b2c0a3b/attachment.pgp>


More information about the ubuntu-users mailing list