<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<div style="direction:ltr; font-family:Tahoma; color:#000000; font-size:10pt">Hi everyone,<br>
<br>
I want to touch on the topic of external repositories for MacPorts again <font size="2">
<span style="font-size:10pt">(related to <a href="https://trac.macports.org/ticket/46954" target="_blank">
https://trac.macports.org/ticket/46954</a>).<br>
<br>
To summarise:<br>
- If I am not mistaken in my interpretation of the previous email exchange, there appear to be use cases for allowing easy addition and removal of external repositories.
</span></font><font size="2"><span style="font-size:10pt"><font size="2"><span style="font-size:10pt">(This is irrespective of whether I can move my Portfiles over to the standard repository.)</span></font><br>
- There is no existing standard mechanism for this in MacPorts.<br>
- There is a little bit of support for using the solution indicated in ticket 46954. Though this approach is considered somewhat hackish.<br>
- We have some agreement that a cleaner approach would be to have something like a /opt/local/etc/macports/sources.conf.d/ path where additional repository configuration files could be added or removed, rather than modifying the master config file directly.
Though there is some concern for handling the prioritisation.<br>
- A long term goal for a generic solution may come with using libsolv for dealing with prioritisation.<br>
<br>
So what should be done about ticket 46954?<br>
Should it be dropped? Accepted? or should the </span></font><font size="2"><span style="font-size:10pt">/opt/local/etc/macports/sources.conf.d/ directory option be implemented first and then
</span></font><font size="2"><span style="font-size:10pt">46954 adjusted to the new scheme?<br>
If the consensus is the latter, then what would be the timeframe for such an update to MacPorts?<br>
<br>
Kind regards.<br>
<br>
Artur<br>
</span></font></div>
</div>
</body>
</html>