Re: Call for arms: Arch Linux D package maintenance

2017-07-12 Thread Wild via Digitalmars-d-announce

On Monday, 10 July 2017 at 23:39:36 UTC, rjframe wrote:
I couldn't find a documented deprecation process, but they do 
deprecate packages; perhaps if that could be pushed forward it 
would allow someone to maintain something in AUR.


I can maintain the packages if they are moved to the AUR. I 
maintain most of the

dlang packages in there already. [1]

I been thinking of applying to become a TU, but haven't gotten 
around to do it. (I will probably do this in the future if needed)


[1] https://aur.archlinux.org/packages/?K=dlang


Re: Call for arms: Arch Linux D package maintenance

2017-07-10 Thread rjframe via Digitalmars-d-announce
On Sun, 09 Jul 2017 21:33:15 +, bachmeier wrote:

> The answer (assuming things are still run the way they
> were back then) is that you're not able to do anything about it. You
> won't see anything done with the official package and you won't be able
> to put anything in AUR because there is an official package.

I couldn't find a documented deprecation process, but they do deprecate 
packages; perhaps if that could be pushed forward it would allow someone 
to maintain something in AUR.


Re: Call for arms: Arch Linux D package maintenance

2017-07-09 Thread bachmeier via Digitalmars-d-announce

On Sunday, 9 July 2017 at 19:56:20 UTC, Seb wrote:


Ouch - so how do we improve the status quo?
It's July, the packages are still listed as orphans [1], 
haven't received the 2.074.1 update and the Arch TUs are 
clearly not interested in maintaining it (its flagged as 
out-of-date since beginning of June). Moreover, with the recent 
move to -fPIC (which currently is in -fPIC), the packages would 
need a rebuilt with -fPIC (see [2]).

Anyone with an idea?

[1] https://www.archlinux.org/packages/community/x86_64/dmd
[2] 
http://forum.dlang.org/post/gpbyhmdsudlmapsvv...@forum.dlang.org


As I wrote elsewhere in this thread, I quit using Arch because of 
related problems. The answer (assuming things are still run the 
way they were back then) is that you're not able to do anything 
about it. You won't see anything done with the official package 
and you won't be able to put anything in AUR because there is an 
official package. Perhaps we can post a pkgbuild on dlang.org.


Re: Call for arms: Arch Linux D package maintenance

2017-07-09 Thread Seb via Digitalmars-d-announce

On Monday, 17 April 2017 at 11:04:11 UTC, R McGuire wrote:

On Thursday, 13 April 2017 at 09:34:00 UTC, Atila Neves wrote:

On Tuesday, 11 April 2017 at 16:17:32 UTC, John Colvin wrote:
On Thursday, 16 February 2017 at 19:58:47 UTC, Rory McGuire 
wrote:

[...]


Any news on this? The arch packages are listed as orphaned.


Same question, and adding that I volunteer to take over.

Atila


Are you involved in Arch?

The update is that Arch TUs are not likely to accept one of us 
that is not very involved in Arch. I've been watching the Arch 
mailing lists a bit and two users that tried to get involved 
were rejected and one user who is _very_ involved and has been 
for years got accepted.


I have tried to contact the last person that built the packages 
to see I could help with the dlang packages but have not 
received a reply yet.



Ouch - so how do we improve the status quo?
It's July, the packages are still listed as orphans [1], haven't 
received the 2.074.1 update and the Arch TUs are clearly not 
interested in maintaining it (its flagged as out-of-date since 
beginning of June). Moreover, with the recent move to -fPIC 
(which currently is in -fPIC), the packages would need a rebuilt 
with -fPIC (see [2]).

Anyone with an idea?

[1] https://www.archlinux.org/packages/community/x86_64/dmd
[2] 
http://forum.dlang.org/post/gpbyhmdsudlmapsvv...@forum.dlang.org


Re: Call for arms: Arch Linux D package maintenance

2017-04-17 Thread R McGuire via Digitalmars-d-announce

On Thursday, 13 April 2017 at 09:34:00 UTC, Atila Neves wrote:

On Tuesday, 11 April 2017 at 16:17:32 UTC, John Colvin wrote:
On Thursday, 16 February 2017 at 19:58:47 UTC, Rory McGuire 
wrote:

[...]


Any news on this? The arch packages are listed as orphaned.


Same question, and adding that I volunteer to take over.

Atila


Are you involved in Arch?

The update is that Arch TUs are not likely to accept one of us 
that is not very involved in Arch. I've been watching the Arch 
mailing lists a bit and two users that tried to get involved were 
rejected and one user who is _very_ involved and has been for 
years got accepted.


I have tried to contact the last person that built the packages 
to see I could help with the dlang packages but have not received 
a reply yet.





Re: Call for arms: Arch Linux D package maintenance

2017-04-13 Thread Atila Neves via Digitalmars-d-announce

On Tuesday, 11 April 2017 at 16:17:32 UTC, John Colvin wrote:
On Thursday, 16 February 2017 at 19:58:47 UTC, Rory McGuire 
wrote:

[...]


Any news on this? The arch packages are listed as orphaned.


Same question, and adding that I volunteer to take over.

Atila


Re: Call for arms: Arch Linux D package maintenance

2017-04-11 Thread John Colvin via Digitalmars-d-announce

On Thursday, 16 February 2017 at 19:58:47 UTC, Rory McGuire wrote:

Hi,

I am planning on asking to become TU for the dlang packages in
community. I've been building and working with the current 
packages
and making my own packages to make sure I know what I'm getting 
in to.
LDC and GDC are matched with the system versions of llvm and 
gcc. If I
can get TU approval I will put time in to these packages and 
hopefully

make some Arch tools that use dlang to try and promote it more.
To learn makepkg and nampac etc I built this [0], it is a set of
PKGBUILD files that are loosely based on the way I use multiple
official dmd compilers on my dev box. Some of my customers use 
older
version of Vibe that do not build on current dmd. I actually 
normally
use /usr/local/ and not /usr/lib for my dmd installation. It 
also has
a little utility for switching between compilers versions, 
similar to

archlinux-java.

[0]: https://github.com/rjmcguire/archlinux-dmd


Any news on this? The arch packages are listed as orphaned.


Re: Call for arms: Arch Linux D package maintenance

2017-02-22 Thread Seb via Digitalmars-d-announce

On Thursday, 16 February 2017 at 19:58:47 UTC, Rory McGuire wrote:

Hi,

I am planning on asking to become TU for the dlang packages in
community. I've been building and working with the current 
packages
and making my own packages to make sure I know what I'm getting 
in to.
LDC and GDC are matched with the system versions of llvm and 
gcc. If I
can get TU approval I will put time in to these packages and 
hopefully

make some Arch tools that use dlang to try and promote it more.
To learn makepkg and nampac etc I built this [0], it is a set of
PKGBUILD files that are loosely based on the way I use multiple
official dmd compilers on my dev box. Some of my customers use 
older
version of Vibe that do not build on current dmd. I actually 
normally
use /usr/local/ and not /usr/lib for my dmd installation. It 
also has
a little utility for switching between compilers versions, 
similar to

archlinux-java.

[0]: https://github.com/rjmcguire/archlinux-dmd


Hi Ruby,

I just saw that you pushed out new versions for LDC and Phobos - 
thanks a lot for doing this!

Your work is highly appreciated :)

If I can get TU approval I will put time in to these packages 
and hopefully make some Arch tools that use dlang to try and 
promote it more.


Awesome! I am really looking forward to this!
Please let us know if there's any way we can help you to make 
this process easier.


Re: Call for arms: Arch Linux D package maintenance

2017-02-16 Thread Vladimir Panteleev via Digitalmars-d-announce

On Thursday, 16 February 2017 at 19:58:47 UTC, Rory McGuire wrote:

I am planning on asking to become TU for the dlang packages in
community. I've been building and working with the current 
packages
and making my own packages to make sure I know what I'm getting 
in to.



Sounds great, good luck!


Re: Call for arms: Arch Linux D package maintenance

2017-02-16 Thread Rory McGuire via Digitalmars-d-announce
On Thu, Feb 16, 2017 at 6:47 PM, Vladimir Panteleev via
Digitalmars-d-announce  wrote:
> On Wednesday, 1 February 2017 at 12:47:51 UTC, Dicebot wrote:
>>
>> As I have previously announced
>> (http://forum.dlang.org/post/o6fbbu$1qli$1...@digitalmars.com), I am stepping
>> down from maintaining Arch Linux packages for D.
>
>
> Hi, wondering what the outcome of this was.
>
> Also, how big is the maintenance burden? Is there more to it than a version
> number bump & push on each release? Perhaps it could be automated or
> integrated into the release process.
>
> FWIW, I've got a few packages on AUR:
> https://aur.archlinux.org/packages/?SeB=m=CyberShadow

Hi,

I am planning on asking to become TU for the dlang packages in
community. I've been building and working with the current packages
and making my own packages to make sure I know what I'm getting in to.
LDC and GDC are matched with the system versions of llvm and gcc. If I
can get TU approval I will put time in to these packages and hopefully
make some Arch tools that use dlang to try and promote it more.
To learn makepkg and nampac etc I built this [0], it is a set of
PKGBUILD files that are loosely based on the way I use multiple
official dmd compilers on my dev box. Some of my customers use older
version of Vibe that do not build on current dmd. I actually normally
use /usr/local/ and not /usr/lib for my dmd installation. It also has
a little utility for switching between compilers versions, similar to
archlinux-java.

[0]: https://github.com/rjmcguire/archlinux-dmd


Re: Call for arms: Arch Linux D package maintenance

2017-02-16 Thread Vladimir Panteleev via Digitalmars-d-announce

On Wednesday, 1 February 2017 at 12:47:51 UTC, Dicebot wrote:
As I have previously announced 
(http://forum.dlang.org/post/o6fbbu$1qli$1...@digitalmars.com), I 
am stepping down from maintaining Arch Linux packages for D.


Hi, wondering what the outcome of this was.

Also, how big is the maintenance burden? Is there more to it than 
a version number bump & push on each release? Perhaps it could be 
automated or integrated into the release process.


FWIW, I've got a few packages on AUR:
https://aur.archlinux.org/packages/?SeB=m=CyberShadow


Re: Call for arms: Arch Linux D package maintenance

2017-02-07 Thread Daniel Kozak via Digitalmars-d-announce
Dne 7.2.2017 v 12:52 Joseph Rushton Wakeling via Digitalmars-d-announce 
napsal(a):



On Thursday, 2 February 2017 at 10:08:19 UTC, Daniel Kozak wrote:

I belive arch would prefer flatpak ;)


Didn't notice this before, but: the good thing about both snap and 
flatpak is one doesn't have to choose between them; these packages can 
coexist on the same system.


So as long as Arch is prepared to have an up to date snapd in its 
repos, snap packages should Just Work for those who want to use them.

Yes that is true ;)


Re: Call for arms: Arch Linux D package maintenance

2017-02-07 Thread Joseph Rushton Wakeling via Digitalmars-d-announce

On Thursday, 2 February 2017 at 10:08:19 UTC, Daniel Kozak wrote:

I belive arch would prefer flatpak ;)


Didn't notice this before, but: the good thing about both snap 
and flatpak is one doesn't have to choose between them; these 
packages can coexist on the same system.


So as long as Arch is prepared to have an up to date snapd in its 
repos, snap packages should Just Work for those who want to use 
them.


Re: Call for arms: Arch Linux D package maintenance

2017-02-06 Thread Joseph Rushton Wakeling via Digitalmars-d-announce

On Thursday, 2 February 2017 at 11:34:42 UTC, Dicebot wrote:

On Thursday, 2 February 2017 at 10:01:04 UTC, qznc wrote:
In another thread [0] Snap packages are discussed. What is the 
view of Arch? If Snap wins, there would be only one package to 
maintain for all distros.


[0] 
https://forum.dlang.org/post/mzklrdgeyymuwmtqz...@forum.dlang.org


There is snapd daemon available in Arch repositories but with 
zero support and guarantees for any actual snap packages. I am 
not aware of any discussions about in TU mail list either.


The main problem right now is that the snapd version is a few 
releases behind and does not support the 'classic' snap 
confinement needed for tools like compilers, dub, etc.  I'll 
probably ping the snapd uploader about this if the situation 
doesn't change soon.  With that dealt with, we can confirm if the 
current ldc2 snap package really does its intended job ;-)


It's my intention to ensure that there are snap packages 
available for all the core D compilers and tools (i.e. dmd, ldc2, 
gdc, rdmd and dub; I'm happy to add to that list if need be).  
This ought to ensure in the long run that there are packages 
available to Arch users (and other distros) even if no one steps 
up to maintain the distro packages.


However, I think it would be a good idea for someone to step up 
to maintain the dedicated Arch packages in any case -- it's 
healthy for D to have a representative inside the Arch community.


Re: Call for arms: Arch Linux D package maintenance

2017-02-02 Thread Rory McGuire via Digitalmars-d-announce
On Thu, Feb 2, 2017 at 1:29 PM, Dicebot via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:

> On Wednesday, 1 February 2017 at 18:32:48 UTC, Rory McGuire wrote:
>
>> I use arch and D every day. I'm willing to volunteer. I keep up to date
>> with all releases and keep multiple dmd versions. If I'm maintaining the
>> packages I'd use them (if I can still switch versions of dmd).
>>
>
> Are you familiar with the PKGBUILD system? Please ping me via
> pub...@dicebot.lv
>

pinged.


Re: Call for arms: Arch Linux D package maintenance

2017-02-02 Thread Dicebot via Digitalmars-d-announce

On Thursday, 2 February 2017 at 10:01:04 UTC, qznc wrote:
In another thread [0] Snap packages are discussed. What is the 
view of Arch? If Snap wins, there would be only one package to 
maintain for all distros.


[0] 
https://forum.dlang.org/post/mzklrdgeyymuwmtqz...@forum.dlang.org


There is snapd daemon available in Arch repositories but with 
zero support and guarantees for any actual snap packages. I am 
not aware of any discussions about in TU mail list either.


Re: Call for arms: Arch Linux D package maintenance

2017-02-02 Thread Dicebot via Digitalmars-d-announce

On Wednesday, 1 February 2017 at 18:32:48 UTC, Rory McGuire wrote:
I use arch and D every day. I'm willing to volunteer. I keep up 
to date with all releases and keep multiple dmd versions. If 
I'm maintaining the packages I'd use them (if I can still 
switch versions of dmd).


Are you familiar with the PKGBUILD system? Please ping me via 
pub...@dicebot.lv


Re: Call for arms: Arch Linux D package maintenance

2017-02-02 Thread Daniel Kozak via Digitalmars-d-announce
I belive arch would prefer flatpak ;)

Dne 2. 2. 2017 11:06 AM napsal uživatel "qznc via Digitalmars-d-announce" <
digitalmars-d-announce@puremagic.com>:

> On Wednesday, 1 February 2017 at 12:47:51 UTC, Dicebot wrote:
>
>> As I have previously announced (http://forum.dlang.org/post/o
>> 6fbbu$1qli$1...@digitalmars.com), I am stepping down from maintaining Arch
>> Linux packages for D.
>>
>> That means there are 3 possibilities:
>>
>> - No one will adopt them and all packages will be moved to AUR
>> - Some existing Trusted User decided to adopt them
>> - Someone from D community decides to become Trusted User and adopts them
>>
>
> In another thread [0] Snap packages are discussed. What is the view of
> Arch? If Snap wins, there would be only one package to maintain for all
> distros.
>
> [0] https://forum.dlang.org/post/mzklrdgeyymuwmtqz...@forum.dlang.org
>


Re: Call for arms: Arch Linux D package maintenance

2017-02-02 Thread qznc via Digitalmars-d-announce

On Wednesday, 1 February 2017 at 12:47:51 UTC, Dicebot wrote:
As I have previously announced 
(http://forum.dlang.org/post/o6fbbu$1qli$1...@digitalmars.com), I 
am stepping down from maintaining Arch Linux packages for D.


That means there are 3 possibilities:

- No one will adopt them and all packages will be moved to AUR
- Some existing Trusted User decided to adopt them
- Someone from D community decides to become Trusted User and 
adopts them


In another thread [0] Snap packages are discussed. What is the 
view of Arch? If Snap wins, there would be only one package to 
maintain for all distros.


[0] 
https://forum.dlang.org/post/mzklrdgeyymuwmtqz...@forum.dlang.org


Re: Call for arms: Arch Linux D package maintenance

2017-02-01 Thread Rory McGuire via Digitalmars-d-announce
On Wednesday, February 1, 2017, Dicebot via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:

> As I have previously announced
> (http://forum.dlang.org/post/o6fbbu$1qli$1...@digitalmars.com), I am
> stepping down from maintaining Arch Linux packages for D.
>
> That means there are 3 possibilities:
>
> - No one will adopt them and all packages will be moved to AUR
> - Some existing Trusted User decided to adopt them
> - Someone from D community decides to become Trusted User and adopts them
>
> First option is definitely the worst one and I don't see any enthusiasm
> regarding second option from existing TUs. Is there anyone willing to
> volunteer for the option three?
>
> I promise all the guidance and help in submitting TU application and
> figuring out maintenance process but there does need to be a volunteer ;)
>
>
I use arch and D every day. I'm willing to volunteer. I keep up to date
with all releases and keep multiple dmd versions. If I'm maintaining the
packages I'd use them (if I can still switch versions of dmd).


Re: Call for arms: Arch Linux D package maintenance

2017-02-01 Thread bachmeier via Digitalmars-d-announce

On Wednesday, 1 February 2017 at 12:47:51 UTC, Dicebot wrote:
As I have previously announced 
(http://forum.dlang.org/post/o6fbbu$1qli$1...@digitalmars.com), I 
am stepping down from maintaining Arch Linux packages for D.


That means there are 3 possibilities:

- No one will adopt them and all packages will be moved to AUR
- Some existing Trusted User decided to adopt them
- Someone from D community decides to become Trusted User and 
adopts them


First option is definitely the worst one and I don't see any 
enthusiasm regarding second option from existing TUs. Is there 
anyone willing to volunteer for the option three?


I promise all the guidance and help in submitting TU 
application and figuring out maintenance process but there does 
need to be a volunteer ;)


It's been quite a while since Arch was my main desktop, so things 
might have changed, in which case please ignore this comment.


The worst outcome is option 3 with someone that is not dedicated 
to the task. One of the reasons I started using Arch was because 
it was continuously updated, allowing me to get the latest 
versions of several packages right after a new release. What I 
found instead was that the TU in charge of the packages wouldn't 
provide updates. Making matters worse, because there was an 
official package, they wouldn't allow it in AUR. Making matters 
worse still, when someone would inquire on the forums there were 
TUs writing lengthy responses telling them to stop whining and 
write their own pkgbuild and anyway how hard is it to compile 
software.


Eventually I gave up because not only was I stuck compiling my 
own software, I was also responsible for making necessary changes 
to pkgbuild files (and that wasn't always just bumping a version 
number).


Hopefully anyone that does step up will think carefully first 
about whether they are willing to make a sufficient time 
commitment. Otherwise we'll lose most Arch users, and that's a 
popular distro.