Re: [Dev] Cleaning up [pcr]

2017-08-08 Thread Isaac David

Isaac David :

looking at libredbdiff i'm noticing that some packages in
[libre] used to replace things which no longer exist in Arch proper
(i.e. non-AUR), and serve no other purpose for Parabola as far as i
can tell. vestiges from a previous age:

javacc
jquery
jquery-ui
psi
spacefm
usermin
webmin
xbmc-pvr-addons-lts
xchat

weigh in if you think there's any reason they shouldn't be disposed of
(in abslibre as well), or if you would like to see them moved to [pcr]


gone
--
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
Tox: 
0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C


___
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev


Re: [Dev] Cleaning up [pcr]

2017-07-29 Thread Isaac David

The [pcr] repository has many packages that haven't been upgraded for
ages, however, they are not marked as outdated. Some of those unused
packages are not even compiled (they are only in the abslibre)


looking at libredbdiff i'm noticing that some packages in
[libre] used to replace things which no longer exist in Arch proper
(i.e. non-AUR), and serve no other purpose for Parabola as far as i
can tell. vestiges from a previous age:

javacc
jquery
jquery-ui
psi
spacefm
usermin
webmin
xbmc-pvr-addons-lts
xchat

weigh in if you think there's any reason they shouldn't be disposed of
(in abslibre as well), or if you would like to see them moved to [pcr]

--
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
Tox: 
0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C


___
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev


Re: [Dev] Cleaning up [pcr]

2017-07-11 Thread bill-auger
as i see it there are a number of important differences between the PCR and the 
AUR - the most notable is that registration is not open to the general public 
as it is on the AUR - from what i understand the only way to get a package into 
the PCR is by pushing it directly to the parabola git instance just like every 
other package - this essentially makes every PCR maintainer an official 
parabola developer doesn't it? - is there any distinction regarding "official" 
and "community-maintained" packages? the "FAQ" page on the wiki says that if 
you want to get a PKGBUILD from AUR into parabola you need to ask a parabola 
hacker to put it there for you - the wording on the "Repositories" wiki page 
however seems to indicate something else:

  "the PCR contains packages maintained by trusted members of the Parabola 
community"

as a side note - the description of the "community" repo talks spcifically abut 
arch and AUR which indicates that this "community" vs "PCR" distinction was not 
planned out thoroughly
 
  "Community contains packages from the AUR which gained enough votes to be 
adopted by an Arch Trusted User"

i assume that for parabola this should instead read:

  "Community contains packages from the PCR which gained enough votes to be 
adopted by an Parabola Trusted User"

are there indeed any "Parabola Trusted Users" who are not also "Official 
Parabola Hackers"? and if so, then how does their access to the main production 
repositories differ from the "Official Parabola Hackers"

from the archwiki:

> Sharing and maintaining packages
> 
> Users can share PKGBUILDs using the Arch User Repository. It does not contain
> any binary packages but allows users to upload PKGBUILDs that can be 
> downloaded
> by others. These PKGBUILDs are completely unofficial and have not been 
> thoroughly
> vetted, so they should be used at your own risk.

secondly as i understand it, the PCR contains both PKGBUILDs and binary 
packages - i am assuming that the raeson for suggesting to remove them now is 
because they take up space - but the AUR is entirely PKGBUILDs which are just 
tiny text files that occupty only a negligable amount of space and therefore 
those could be kept available indefinitely - the only valid reason for removing 
them (other than freedom issues) would be if they are so old that will not 
build any more

from the archwiki:

> What is the difference between the Arch User Repository and the community 
> repository?
> 
> The Arch User Repository is where all PKGBUILDs that users submit are stored,
> and must be built manually with makepkg. When PKGBUILDs receive enough 
> community
> interest and the support of a TU, they are moved into the community repository
> (maintained by the TUs), where the binary packages can be installed with 
> pacman. 

so i am suggesting that the PCR stores only PKGBUILDs that are installable at 
any time but only with the makepkg tool not directly in binary form with pacman 
- and that anyone is allowed to publish these without having the any 
credentials on the main production repo - in this way those package can remain 
available even if they are not maintained by anyone (for as long as they do not 
become broken) then parabola can state that those are "unofficial" and possibly 
broken or unmaintained so use at you own risk


signature.asc
Description: PGP signature
___
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev


Re: [Dev] Cleaning up [pcr]

2017-07-10 Thread Megver83
El 10/07/17 a las 14:37, fauno escribió:
> bill-auger  writes:
> 
>> this seems like a good time to ask why exactly does parabola need both
>> "Community" and "PCR" - i undestand the distinction of "Community" and
>> "AUR" in arch but in parabola these seem to be serving exactly the
>> same purpose
>>
>> perhaps a solution here is to make the "PCR" be user-maintained like
>> the AUR - then those orphaned packages can still be available using
>> makepkg but will not be a burden on the main production machines
> 
> this is exactly why we created [pcr] :P
> 
> +1 to remove packages, sending a ping to maintainers before?

Or better the same maintainers remove their own unmaintained pkgs, and
if it's from someone who left, then go ahead :)

> 
> 
> 
> 
> ___
> Dev mailing list
> Dev@lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev
> 



signature.asc
Description: OpenPGP digital signature
___
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev


Re: [Dev] Cleaning up [pcr]

2017-07-10 Thread fauno
bill-auger  writes:

> this seems like a good time to ask why exactly does parabola need both
> "Community" and "PCR" - i undestand the distinction of "Community" and
> "AUR" in arch but in parabola these seem to be serving exactly the
> same purpose
>
> perhaps a solution here is to make the "PCR" be user-maintained like
> the AUR - then those orphaned packages can still be available using
> makepkg but will not be a burden on the main production machines

this is exactly why we created [pcr] :P

+1 to remove packages, sending a ping to maintainers before?


-- 
P)


signature.asc
Description: PGP signature
___
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev


Re: [Dev] Cleaning up [pcr]

2017-07-10 Thread bill-auger

this seems like a good time to ask why exactly does parabola need both 
"Community" and "PCR" - i undestand the distinction of "Community" and "AUR" in 
arch but in parabola these seem to be serving exactly the same purpose

perhaps a solution here is to make the "PCR" be user-maintained like the AUR - 
then those orphaned packages can still be available using makepkg but will not 
be a burden on the main production machines


signature.asc
Description: PGP signature
___
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev


Re: [Dev] Cleaning up [pcr]

2017-07-10 Thread Andreas Grapentin

+1

I think we could have a mechanism on [pcr] that packages that have not
been rebuild in X amount of time are marked as candidates for removal.

On Sun, Jul 09, 2017 at 07:15:20PM -0400, Megver83 wrote:
> Hi, I'll go direct to the point. The [pcr] repository has many packages
> that haven't been upgraded for ages, however, they are not marked as
> outdated. Some of those unused packages are not even compiled (they are
> only in the abslibre), I found a few when I began to adopt some packages
> which even had MIPS in the "arch" array of their PKGBUILDs. If those are
> ancient packages that have not been marked as outdated, it's likely
> because no one installs them anymore, so I think that for that reason we
> should remove those until someone requests it.
> 
> In the free time that I don't have I will hunt some :D
> -- 
> GPG: 0x227CA7C556B2BA78
> 




> ___
> Dev mailing list
> Dev@lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev


-- 

--
my GPG Public Key: https://files.grapentin.org/.gpg/public.key
--


signature.asc
Description: PGP signature
___
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev