package creation failure

[John Marino]

On 9/29/2015 7:31 PM, Charles Musser wrote:
> I tried this:
> 
> xo% sudo make clean ; sudo make stage-qa
> ===>  Cleaning for rdnssd-1.0.0
> ====> Running Q/A tests (stage-qa)
> cd: /usr/obj/dports/dns/rdnssd/work/stage: No such file or directory
> find: /usr/obj/dports/dns/rdnssd/work/stage: No such file or directory
> find: /usr/obj/dports/dns/rdnssd/work/.PLIST.mktmp: No such file or directory
> find: /usr/obj/dports/dns/rdnssd/work/stage: No such file or directory
> find: /usr/obj/dports/dns/rdnssd/work/stage: No such file or directory
> find: /usr/obj/dports/dns/rdnssd/work/stage: No such file or directory
> find: /usr/obj/dports/dns/rdnssd/work/stage: No such file or directory
> 
> Doing a "make stage" after "make clean" allowed the "make stage-qa" to
> complete successfully. It didn't find any problems. But is that the correct
> sequence of steps?

Yes.  I recall now that stage-qa doesn't have prerequisite steps.  You
have to call "make stage" before "make stage-qa"


> Also, a side question. I'm doing everything with sudo because all these
> directories are owned by root/wheel and have 0755 permissions. What
> do most people do when working on ports? Use sudo, or chmod/chown
> the directory trees so that the non-root accounts can write files?

Nobody at all uses sudo.  The pkg program handles ownership and
automatically.  The "install" macros set the right permissions.

You should take a momemt and go through the porters handbook on the
FreeBSD site.  Everything is pretty well documented.



>> In general I limit "dports-only" packages to those that clearly cannot
>> or will not be accepted in freebsd ports.  Generally what is useful for
>> use is also useful to dragonfly and should be formally maintained.
> 
> My intent is to create what I think you're describing: an entity that exists
> in the DPorts collection and can be installed with "pkg install rdnssd".
> I wasn't aware of "dports-only" packages. Am I going about creating an
> installable package in the correct way?


The DPorts Collection is essentially the FreeBSD Ports Collection with
changes overlaid (usually in the form of extra files and patches to the
software, but sometimes patches to the port itself).   While we have the
ability to have a port that FreeBSD doesn't, we usually put new ports in
the FreeBSD collection and let it trickle back down.

John