Compatability with FreeBSD Ports

Hiten Pandya hmp at backplane.com
Mon Aug 15 10:10:22 PDT 2005


On that note, DR and others, please do not commit the pkgsrc utilities 
into base just yet.  Make use of the nrelease framework in the same way 
done for the installer code so we don't duplicate on things.

			Hiten Pandya
			hmp at xxxxxxxxxxxxx
Matthew Dillon wrote:
:
:On 15 Aug 2005 00:17:07 -0000, Andreas Hauser <andy at xxxxxxxxxxxxxxx> wrote:
:> dillon wrote @ Fri, 12 Aug 2005 09:27:44 -0700 (PDT):
:> 
:> >     So the answer is no... we are going to have to move to (almost
:> >     certainly) pkgsrc and fix whatever issues we have with it.
:> 
:> Well, currently ports are still better than pkgsrc. And the way pkgsrc is
:> being forced upon us, politically instead of technically, will fail.
:> 
:> 
:> Andy
:
:What problems do you see with pkgsrc ?
:
:I was planning on committing the pkgsrc utils into the DFly tree this
:week, but perhaps there are some issues that people have with pkgsrc I
:am not aware...
:
:-DR

    I think we have to move forward and pkgsrc is the way to do it.
    It may not be perfect, but there are enough people on the bandwagon
    that we can make work, and work well, and not be sitting out all alone
    (relative to the other BSDs) trying to support it.
    We have to decide on something and I know I haven't done a good job
    helping out on the ports/packages issue.  Lets decide to move forward
    with pkgsrc and throw all our weight behind it.  

    We absolutely need a packaging system for the 1.4 release, which I
    expect is going to occur in December.  With Joerg almost through with
    the last of the ABI changes (to dirent), this is the time to do it.  

    We aren't throwing away ports... ports is fairly well self-contained,
    even if it doesn't do a good job outside of FreeBSD.  But it is clear
    to me that there are a ton more people willing to work on and support
    pkgsrc in the context of DragonFly then there are willing to work on 
    and support ports.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>





More information about the Users mailing list