Skip to content

pkgdev mask: add subcommand support for semi-automated package.mask mangling #6

Closed

Description

@radhermit

Initial implementation should target just profiles/package.mask additions/removals, with possibly any existing profile path being supported long-term.

Activity

  1. changed the title [-]pkgdev mask: add subcommand support for semi-automated package.mask additions[/-] [+]pkgdev mask: add subcommand support for semi-automated package.mask mangling[/+] on Feb 27, 2021
  2. thesamesam commented on Mar 4, 2021

    @thesamesam
    Member

    Also, could check commits for the first line added in a hunk to package.mask for correct date. This may be a bit fiddly though.

  3. thesamesam commented on Mar 22, 2021

    @thesamesam
    Member

    There's another consequence of a standardised package.mask format: we could enable mass-treecleaning of a whole block, although this is easy to script with the package names:

    grep -v "#" /tmp/list | xargs -L 1 -d "\n" xargs -0 bash -c 'git rm -rf ${0} ; pkgdev commit'
    
  4. radhermit commented on Mar 22, 2021

    @radhermit
    ContributorAuthor

    There's another consequence of a standardised package.mask format: we could enable mass-treecleaning of a whole block, although this is easy to script with the package names:

    grep -v "#" /tmp/list | xargs -L 1 -d "\n" xargs -0 bash -c 'git rm -rf ${0} ; pkgdev commit'
    

    I partially wrote pkgdev to provide an alternative to terrible one-liners. 😉

  5. thesamesam commented on Mar 22, 2021

    @thesamesam
    Member

    I need to keep showing you horrors then! Feels like a corruption of pkgdev to use it in one.

  6. radhermit commented on Mar 22, 2021

    @radhermit
    ContributorAuthor

    Rough draft added in 9ce008b, note that this requires some cleanup of the current file to be able to sanely handle automatically modifying it with the current entry "standard".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions