tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: pkgsrc/mk/flavor/pkg




To: Tobias Nygren <tnn%NetBSD.org@localhost>

Subject: Re: CVS commit: pkgsrc/mk/flavor/pkg

From: Jens Rehsack <rehsack%googlemail.com@localhost>

Date: Mon, 14 Jun 2010 14:27:07 +0000


On 06/13/10 09:34, Tobias Nygren wrote:

The osabi dummy package itself seems to me like a rather kludgy solution
to a subset of a difficult problem. From the perspective of updating
it causes more problems than it solves. Besides, when you try to install
a package build for a different OS release you already get a warning
from the tools.


But the warning is not all what is needed - a sane way to update them
is needed. I like the idea of the osabi dummy package, it allows to strip
extra information from PKG_NAME and with it, better dependency tracking
(e.g. when adding a perl module for lsof).
Before osabi dummy package, it was required to update packages with
OSABI dependencies to install dependent packages - regardless if the
work fine or not.

Best regards,
Jens


References:

Re: CVS commit: pkgsrc/mk/flavor/pkg
From: Thomas Klausner

Re: CVS commit: pkgsrc/mk/flavor/pkg
From: Joerg Sonnenberger

Re: CVS commit: pkgsrc/mk/flavor/pkg
From: Joerg Sonnenberger

Re: CVS commit: pkgsrc/mk/flavor/pkg
From: Greg Troxel

Re: CVS commit: pkgsrc/mk/flavor/pkg
From: Tobias Nygren




Prev by Date: Re: Patch name changes

Next by Date: daily pkgsrc CVS update output

Previous by Thread: Re: CVS commit: pkgsrc/mk/flavor/pkg

Next by Thread: Re: CVS commit: pkgsrc/mk/flavor/pkg

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index