[HEADSUP] Staging, packaging and more
bapt at freebsd.org
Tue Oct 8 09:44:40 UTC 2013
On Tue, Oct 08, 2013 at 12:38:22PM +0300, Andrew W. Nosenko wrote:
> On Tue, Oct 8, 2013 at 11:47 AM, Baptiste Daroussin <bapt at freebsd.org> wrote:
> > Concerning the fact that you need a couple of new packages to be able to
> > actually build something out github or whatever, this is a developer problem and
> > doing pkg install gtk2-dev is not complicated at all.
> While installing gtk2-dev is not hard indeed, finding the name of
> package, which you need (gtk2-dev in your example) may be much harder.
> Just an example:
> Ubuntu has a package for curl (commandline utility):
> curl (commandline utility) is a thin wrapper around libcurl, libcurl
> is registered as a dependency. No problems yet, just go through
> hypelink. http://packages.ubuntu.com/precise/libcurl3
> Now, can you say me, what package should I install for obtain headers,
> .pc, debug symbols and other developer-related stuff for that libcurl?
> Not some libcurl, but that specific libcurl, which was fetched as
> dependency of the curl (commandline utility)?
> It just a fear. My fear. Fear that possibility to create
> packages/subpackages may lead to creating them randomly, and these
> randomly created packages/subpackages may lead to the same problems as
> demonstrated above.
> And, seems, I'm not alone in that.
Who spoke about reproducing what debian does? So because some people are doing
things the wrong way now, we should not try to do it the right way?
Sure if we one day decide to go to sepate packages we should go along with a
policy about naming the packages. For example in that case we would probably
No policy has been written yet, and as I said earlier we have no yet ready for
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
More information about the freebsd-ports