On Sep 24, 2014, at 12:23 AM, Marko Käning wrote: > > I was in the firm believe that our buildbots would somehow filter out commits > to user directories > and start building in case they find a valid and somehow updated MacPorts > tree in there. > > That’s why I created my own user dir after all: > > [07:03] <irker326> [email protected] * > https://trac.macports.org/changeset/125673 /users/HANDLE: > [07:03] <irker326> Create user repository for HANDLE > > and then added a new port in there > > [07:11] <irker326> [email protected] * > https://trac.macports.org/changeset/125674 /users/HANDLE/ (9 files in 5 > dirs): > [07:11] <irker326> users/HANDLE/dports/kde/konveration-devel: introduce > devel port for konversation > > assuming that the buildbots will start building this new port for me right > away on all OSX versions... > > > Looks like my assumption was wrong, since nothing happened. :(
I don't know how the buildbot was set up, but I always assumed it built ports in the main dports tree only. You're saying you're able to force it to build ports in your users tree somehow? If so, I would be worried that it would publish binary packages of those pre-release ports. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
