Tentative feature request
Philip M. Gollucci
pgollucci at p6m7g8.com
Thu Oct 20 19:16:41 EDT 2011
Really easy way to do this is keep your list of leap ports since you
seem to know what they are.
delete from build_ports, port_depencdies where build_id = x
for p in list;
100% everytime, no fancy logic
On 10/18/11 08:29, Matt Dawson wrote:
> On Tuesday 18 Oct 2011 07:57:15 Ion-Mihai Tetcu wrote:
>> On Mon, 17 Oct 2011 18:44:29 +0100
>> Matt Dawson <matt at chronos.org.uk> wrote:
>>> On Monday 17 Oct 2011 17:01:02 Joe Marcus Clarke wrote:
>>>> On 10/17/11 9:25 AM, Matt Dawson wrote:
>>>>> Hi all,
>>>>> Is there an easy way to implement something akin to
>>>>> on a tinderbox? I'm finding that I have all manner of cruft
>>>>> in my builds that were once relied upon by other ports, only
>>>>> to fall by the wayside as those ports got superseded or
>>>>> became orphaned. Removing the leaf ports is easy; removing
>>>>> their then useless dependencies is a adventure in SQL and
>>>>> much trial and error.
>>>>> Just and idea...
>>> Meh, dyslexic fingers. *An* idea...
>>>> tc tbcleanup is a good thing to run after a tinderbuild. This
>>>> can give you a cleaner environment and recover quite a bit of
>>>> disk space.
>>> True and I do so, although disk space isn't my overriding concern
>>> at this point. What concerns me is the time taken to build
>>> unnecessary ports by leaving leftover dependencies in place.
>>> Something like pkg_cutleaves could cull the leftovers and
>>> streamline future builds by getting rid of, for example, libs
>>> that are no longer required.
>> Umm? The build is reset to pristine each time.
> Right, I'm obviously not making my point clear. Say you add, for
> example, the KDE-SC metaport to your desktop build. Now, somewhere
> down the line you stop using KDE and migrate to Enlightenment. You
> ./tc rmPort -d x11/kde4. That still leaves all the dependencies that
> you no longer need being built every time you run a tinderbuild and
> wasting (FSVO wasting) time compiling things you don't need. My tindy
> makes packages for use on my networks as well as testing ports that I
> maintain. Building things I don't need is a waste of CPU cycles.
> What I'd like is a way to rmPort kde4 *AND* all its dependencies that
> are no longer needed for other leafnode (leafnode being things that
> aren't dependencies, not $PORTSDIR/news/leafnode) ports. I believe
> there's a table in the SQL framework that records deps, but it does so
> with port numbers which makes manual extraction a chore. Something
> like ./tc rmPort -r -d x11/kde4 where -r = remove dependencies no
> longer used by any other port, i.e. if there are no more entries in
> its row in the deps table once the leaf port is removed. Is that any
> For the record, KDE-SC was pulled out of my behind as an example of a
> port with huge reams of pull-in deps. I use it on my desktops as the
> preferred DM, YMMV.
> tinderbox-list at marcuscom.com mailing list
> To unsubscribe, send any mail to "tinderbox-list-unsubscribe at marcuscom.com"
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci at p6m7g8.com) c: 703.336.9354
VP Infrastructure, Apache Software Foundation
Committer, FreeBSD Foundation
Consultant, P6M7G8 Inc.
Director Operations, Ridecharge Inc.
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
More information about the tinderbox-list