Re: buildpath conf variable

2016-09-27 Thread René J . V . Bertin 
On Monday September 26 2016 11:20:20 Brandon Allbery wrote:

> > I can't guarantee this won't mess something up, but I think you can
> > already delete the /opt/local/var/macports/build directory and replace it a
> > symlink to another volume

> Works fine. Did that on my MacBook Air.

It seems to be working for me too now, but I think I had destroot warnings or 
errors about things being installed outside of ${prefix} before. Is that 
possible, maybe a limitation of a previous MacPorts version?

R.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: buildpath conf variable

2016-09-26 Thread René J . V . Bertin 
On Monday September 26 2016 12:59:17 Ken Cunningham wrote:

> At $0.50 (canadian) per GB, I put them in most of my systems -- even a 120GB 
> version in my Beige G3 running MacOS 9.2.2. Now that is something to see!

The figure is the same here, except they're Euros. The 1Tb disk in my MBP came 
in at about 0.07€/Gb. Not a factor 10 anymore, but close enough.

The cheap Linux notebook I offered myself a few months ago came with a Seagate 
SSHD. A bit more expensive that the Hitachi (so-called) 1Tb hybrid in my Mac, 
possibly not as reliable, but I have been pleased with its speed.

R.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: buildpath conf variable

2016-09-26 Thread Ken Cunningham 

On 2016-09-26, at 1:07 AM, René J.V. Bertin wrote:

> Hi,
> 
> I know that more and more people (esp developers?) are using SSDs and that 
> for them fragmentation starts hitting only when it's the free space that's 
> really severely fragmented.


The SSD was the single most impressive speed bump for MacOSX I've seen in a 
very long time.

At $0.50 (canadian) per GB, I put them in most of my systems -- even a 120GB 
version in my Beige G3 running MacOS 9.2.2. Now that is something to see!

Ken



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: buildpath conf variable

2016-09-26 Thread Lawrence Velázquez 
> On Sep 26, 2016, at 7:19 AM, René J.V. Bertin  wrote:
> 
>> On Monday September 26 2016 04:45:19 Ryan Schmidt wrote:
>> 
>> Most users use Macs with a single volume, so I don't think a patch
>> for this is of general interest.
> 
> Can't the same be said for portdbpath?

Yes. I don't know the rationale for this setting, but if it were
proposed today I would object to it as too niche.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: buildpath conf variable

2016-09-26 Thread Brandon Allbery 
On Mon, Sep 26, 2016 at 5:45 AM, Ryan Schmidt 
wrote:

> I can't guarantee this won't mess something up, but I think you can
> already delete the /opt/local/var/macports/build directory and replace it a
> symlink to another volume


Works fine. Did that on my MacBook Air.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: buildpath conf variable

2016-09-26 Thread René J . V . Bertin 
On Monday September 26 2016 04:45:19 Ryan Schmidt wrote:

> I can't guarantee this won't mess something up, but I think you can already 
> delete the /opt/local/var/macports/build directory and replace it a symlink 
> to another volume.

That's what I'm preparing my system to test, but I seem to recall I tried it 
once already an went back...

> Most users use Macs with a single volume, so I don't think a patch for this 
> is of general interest.

Can't the same be said for portdbpath? Even with a single partition you could 
have multiple virtual volumes, or a (bloody fast) SD card in the cardreader.

R.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

buildpath conf variable

2016-09-26 Thread René J . V . Bertin 
Hi,

I know that more and more people (esp developers?) are using SSDs and that for 
them fragmentation starts hitting only when it's the free space that's really 
severely fragmented. I have no experience in that area, and do not currently 
have the budget to obtain that experience.

Either way, it seems to me that it might be an interesting idea to make it 
possible (easier) to put the build directory on a separate volume (interesting 
for anyone building a lot from source). This removes a big source of free space 
fragmentation (on disks where fragmentation is an issue), but in general helps 
keep ${prefix} cleaner. It can also help keeping log files more compact and 
thus more readable if a shorter base path is chosen.

Is this an idea that would stand a chance being considered for "base", IOW, 
should I file a wishlist ticket on trac?

In fact I have an untested hunch that at least for my own purposes it could be 
useful to have separate trees (and thus potentially separate volumes) for 
source.dir and build.dir/destroot.dir, where possible ... but I also have a 
hunch that would be more anyone could ask for :)

Cheers,
René
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev